Explore the test library

Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.

Filter the library

SearchTypeCategorySubcategoryFormatUse caseIndustryWorkflowValidityEditable workspaceDestination platformBrowser test targetSort

5297 results

Page 50 of 221; 24 results per page.

Show the canonical directory

CSV with Duplicate Headers

A small CSV whose header row repeats the column name id: a common importer failure mode.

File: CSV · Edge Cases · 2 rows
Use case: CSV parsingError handling

CSV with Leading-Zero Identifiers

SKU identifiers that start with zeros. Spreadsheet tools often coerce these to numbers and drop the zeros. Keep them as text.

File: CSV · Edge Cases · 3 rows
Use case: CSV parsingData import

CSV with Mixed Null Representations

A CSV where missing values are written seven different ways (empty string, NULL, NA, N/A, null, None, and a dash) across text and numeric columns. A fixture for testing null-detection and coercion in CSV importers.

File: CSV · Edge Cases · 8 rows
Use case: CSV parsingError handling+1

CSV with Mixed Timestamp Formats

A CSV listing timestamps in eleven formats: ISO 8601 with Z and numeric offsets, millisecond precision, naive local, date-only, Unix epoch in seconds and milliseconds, US AM/PM, and RFC 1123. A fixture for testing date parsing and timezone normalisation.

File: CSV · Edge Cases · 11 rows
Use case: CSV parsingError handling+1

CSV with Mixed-Type Columns

A CSV whose 'value' column mixes integers, floats, scientific notation, dates, hex, thousands separators, and whitespace, and whose 'flag' column mixes a dozen boolean spellings. A torture test for type inference and schema detection.

File: CSV · Edge Cases · 12 rows
Use case: CSV parsingError handling+1

CSV: Cue Timing Report

Per-cue timings and text metrics for the shared cue list, as a caption QC tool would export them: start, end, duration, line count and character count. Useful as the expected output when testing a caption analyser, and as a quick way to check reading-rate calculations against known values.

File: CSV · Index · 5 rows
Use case: Subtitle parsingVideo QA+1

CSV: Hash Comment Lines

A CSV with # comment lines mixed among data: common in scientific exports; tests comment skipping.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

CSV: ISO-8859-1 (Latin-1)

A Latin-1 CSV with high-bit accented characters, for legacy 8-bit charset detection.

File: CSV · Encodings · 2 rows
Use case: CSV parsingEncoding detection

CSV: Mixed CRLF and LF

A CSV that mixes CRLF and LF row endings within one file: newline normalisation fixture.

File: CSV · Encodings · 3 rows
Use case: CSV parsingEncoding detection

CSV: Pipe Delimiter

A pipe-delimited (| ) tabular file, for testing non-comma delimiter autodetection.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

CSV: Quoted Embedded Newlines

A CSV with a quoted field that contains an embedded newline: a classic RFC 4180 parser stress case.

File: CSV · Encodings · 2 rows
Use case: CSV parsingError handling

CSV: Ragged Column Counts

Rows with differing field counts, for testing how importers pad, truncate, or error on ragged CSV.

File: CSV · Encodings · 3 rows
Use case: CSV parsingError handling

CSV: Semicolon Delimiter (EU)

European-style CSV using semicolons as delimiters and comma decimals: a common locale edge case.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

CSV: Shift-JIS Japanese

A Shift-JIS encoded Japanese CSV, for CJK charset detection and Shift-JIS→UTF-8 conversion in importers.

File: CSV · Encodings · 2 rows
Use case: CSV parsingEncoding detection+1

CSV: Single Column

A one-column CSV of email addresses: edge case for delimiter sniffers that expect commas in every row.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

CSV: UTF-16 BE with BOM

UTF-16 big-endian CSV with BOM, for byte-order detection in tabular importers.

File: CSV · Encodings · 3 rows
Use case: CSV parsingEncoding detection

CSV: UTF-16 LE with BOM

The same three data rows as UTF-16 little-endian with a BOM, wide-character CSV decoding fixture.

File: CSV · Encodings · 3 rows
Use case: CSV parsingEncoding detection

CSV: UTF-8 with BOM

A CSV prefixed with a UTF-8 BOM (EF BB BF) and accented / CJK cells, for testing BOM-aware importers.

File: CSV · Encodings · 3 rows
Use case: CSV parsingEncoding detection+1

CSV: Windows-1252 (CP1252)

A CP1252 CSV using the 0x80–0x9F range (smart quotes, euro, bullet) that Latin-1 misreads.

File: CSV · Encodings · 2 rows
Use case: CSV parsingEncoding detection

Cucumber JSON: Failing Step with Stack Trace

One step of one scenario fails with an assertion message and a stack frame; every other step passes. In cucumber.json a scenario has no status of its own (it is failed if any of its steps is), so this file catches reporters that look for a scenario-level field that does not exist.

File: JSON · Bdd · UTF-8
Use case: JSON parsingError handling+1· Conversion set

Cucumber JSON: Passing Checkout Report

The legacy cucumber.json report for the same run: the format nearly every BDD dashboard still ingests. Durations are in nanoseconds here and in a nested {seconds, nanos} object in the messages twin, which is the single most common unit bug when converting between the two.

File: JSON · Bdd · UTF-8
Use case: JSON parsingConversion testing+1· Conversion set

Cucumber JSON: Undefined, Pending and Skipped Steps

The three non-failure statuses BDD runners produce and dashboards routinely collapse into "failed": undefined (no step definition matched), pending (explicitly unimplemented) and skipped (never attempted). Whether the run is red depends on the runner's strict setting, which is exactly the decision this file forces.

File: JSON · Bdd · UTF-8
Use case: JSON parsingError handling+1· Conversion set

Cucumber JUnit XML: Checkout Run

The same six pickles reported as JUnit XML, which is what a BDD suite hands to a generic CI dashboard. One <testcase> per pickle means the three expanded outline rows appear as three tests with identical names, enough to break any store keyed on name alone.

File: XML · Bdd · UTF-8
Use case: Conversion testingLog parsing+1· Conversion set

Cucumber Messages: Failing Run (NDJSON)

The messages twin of the failing run: one testStepFinished carries status FAILED with both a human message and a structured exception object, and testRunFinished reports success false. Comparing it with the passing stream in the other group isolates exactly which envelopes a failure changes.

File: NDJSON · Bdd · UTF-8
Use case: JSON parsingError handling+1· Conversion set