JsonpathToJq conformance gaps: remaining 458 skipped tests

[stalep]

After issue #72 (tokenizing parser) and subsequent bug fixes, jsonpath-to-jq conformance stands at 100/558 (17.9%). The remaining 458 skipped tests break down into distinct categories, prioritized by effort and impact.

High-value, low-effort (36 tests)

Category	Count	Approach
PG17 string methods	32	.lower() → ascii_downcase, .upper() → ascii_upcase, .ltrim()/.rtrim() → ltrimstr/rtrimstr, .replace() → gsub, .initcap()/.btrim()/.split_part() → custom jq defs
is unknown	4	Currently == null; needs == null or . == false or similar three-valued logic

Medium-effort (43 tests)

Category	Count	Approach
Semantic diffs	27	Mixed: type guards for .string()/.boolean() on arrays, .bigint()/.integer() needing tonumber | floor, three-valued comparison logic, like_regex flag "q" literal escaping
Runtime errors	16	Type-mismatch guards: .keyvalue() on non-objects, .double()/.bigint() on arrays/strings need try wrappers

Hard / deferred (379 tests)

Category	Count	Notes
Expects PostgreSQL error	209	Could partially test that jjq also errors, but exact error messages differ
Datetime methods	97	.datetime(), .date(), .time(), .timestamp(), .time_tz(), .timestamp_tz() — need jq date function implementations
Path variables	70	$varname parameter passing — requires API change to accept variable bindings
Conversion failures	3	2 are \B in regex (jq does not support), 1 is arithmetic-in-brackets

Tracking

Conformance is tracked automatically via JsonpathConformanceTest using assumeTrue — any improvement is immediately visible in the test count.

Related

• JsonpathToJq: explore tokenizing parser to replace string-replacement approach #72 — tokenizing parser (done)
• JsonpathToJq: missing tests, bug fixes, and feature gaps #71 — Phase 1-4 conformance improvements (done)

[stalep]

Tier 1 implemented — conformance 100 -> 123/558 (22.0%)

String methods (+23 tests)

Added 8 PG17 string methods to the tokenizing translator:

Method	Translation	Tests gained
.lower()	ascii_downcase	3
.upper()	ascii_upcase	3
.ltrim() / .ltrim(chars)	sub("^[chars]+"; "")	3
.rtrim() / .rtrim(chars)	sub("[chars]+$"; "")	2
.btrim() / .btrim(chars)	ltrim + rtrim	2
.replace(old, new)	gsub(old; new)	4
.initcap()	split + capitalize + join	2
.split_part(sep, N)	split(sep)[N-1]	1
Chained methods (.lower().upper().replace())	Piped	3

9 string method tests still skip:

• 5 due to type-mismatch inputs (applying string methods to numbers/arrays — PG returns error, jq throws)
• 2 from chained methods with starts with (parser issue with mixed method + keyword)
• 2 from initcap on inputs with non-space whitespace

is unknown (0 additional tests)

Removed the skip filter. The translation (| . == null) is in place but the 4 test cases involve division-by-zero and type-mismatch comparisons that throw errors in jq rather than producing null. These need try-catch wrappers for correct behavior.

Updated breakdown

Category	Count	Change
expects_error	209	—
datetime_methods	97	—
variables	70	—
semantic_diff	27	—
runtime_error	~25	+9 (from string method type mismatches + is_unknown)
string_methods	0	-32 (moved to passing or runtime_error)
is_unknown	0	-4 (moved to runtime_error)
conversion_failed	3	—
Total skipped	435	-23
Passing	123	+23