CSV / TSV parsing
12 / 12 passed
CSV / JSON compatibility: 21 / 21 passed
This report exercises the pure parser and serializer module used by the FileNest production converter. It shows that the listed fixtures pass for the pinned production version without stretching that result into a claim about speed, every browser or every CSV dialect.
Result
21 / 21 assertions passed
Runner: Node.js 22.16.0 · node:test. Production commit: 8b380532. Parser module blob: 34345ac3.
JSON input shape
4 / 4 passed
CSV / TSV / JSON serialization
5 / 5 passed
Fixture coverage
What was actually checked
Basic CSV rows and columns
Status: passed. This assertion was executed against the production parser module identified above.
Comma inside a quoted field
Status: passed. This assertion was executed against the production parser module identified above.
Escaped double quotes
Status: passed. This assertion was executed against the production parser module identified above.
Newline inside a quoted field
Status: passed. This assertion was executed against the production parser module identified above.
Windows CRLF line endings
Status: passed. This assertion was executed against the production parser module identified above.
TSV tab delimiter
Status: passed. This assertion was executed against the production parser module identified above.
Blank header fallback to column_N
Status: passed. This assertion was executed against the production parser module identified above.
Duplicate headers preserved as name / name_2
Status: passed. This assertion was executed against the production parser module identified above.
Deterministic numbering for three duplicate headers
Status: passed. This assertion was executed against the production parser module identified above.
Extra row cells preserved as column_N
Status: passed. This assertion was executed against the production parser module identified above.
Short rows padded with empty values
Status: passed. This assertion was executed against the production parser module identified above.
Unclosed quoted field rejected explicitly
Status: passed. This assertion was executed against the production parser module identified above.
Single JSON object accepted
Status: passed. This assertion was executed against the production parser module identified above.
Array of JSON objects accepted
Status: passed. This assertion was executed against the production parser module identified above.
JSON scalar rejected
Status: passed. This assertion was executed against the production parser module identified above.
Array of JSON scalars rejected
Status: passed. This assertion was executed against the production parser module identified above.
CSV output quotes fields containing commas
Status: passed. This assertion was executed against the production parser module identified above.
CSV output escapes double quotes
Status: passed. This assertion was executed against the production parser module identified above.
TSV output delimiter
Status: passed. This assertion was executed against the production parser module identified above.
Pretty-printed JSON output
Status: passed. This assertion was executed against the production parser module identified above.
Nested object preserved as JSON text in CSV
Status: passed. This assertion was executed against the production parser module identified above.
Scope limits
What 21 / 21 does not mean
- This is not a browser or device compatibility matrix.
- It does not measure conversion speed, peak memory use or maximum file size.
- It does not exercise file pickers, downloads, ZIP packaging, accounts, quotas or billing.
- It is not an RFC 4180 certification and does not claim to cover every real-world CSV dialect.
These exclusions are part of the result, not fine print. Browser matrices, performance work or large-file testing require their own method, environment and results rather than extrapolating from this fixture count.