Novus Examples, Real, documented example files for testing

JUnit XML: Phpunit Dialect (phpunit)

The same 12-case Novus Checkout run written the way PHPUnit 11.2 --log-junit writes it. PHPUnit nests per-class suites inside a named parent suite and adds an assertions count that no other dialect reports. All eight dialect files in this group report 12 tests, 1 failure, 1 error and 1 skip, so a JUnit parser can be held to identical totals across every producer.

File: XML · Junit XML · UTF-8
Use case: Conversion testingError handling+1· Conversion set

JUnit XML: Properties Block with Awkward Values

A <properties> block holding an empty value, an escaped ampersand in a branch name and a JVM options string with spaces. Use it to check that build metadata survives extraction with its entities unescaped exactly once.

File: XML · Junit XML · UTF-8
Use case: Metadata testingConfig parsing+1· Conversion set

JUnit XML: Pytest Dialect (pytest)

The same 12-case Novus Checkout run written the way pytest 8.2 --junitxml writes it. pytest emits a single <testsuite name="pytest"> whose classname is the dotted module path, and decorates each case with file and line attributes. All eight dialect files in this group report 12 tests, 1 failure, 1 error and 1 skip, so a JUnit parser can be held to identical totals across every producer.

File: XML · Junit XML · UTF-8
Use case: Conversion testingError handling+1· Conversion set

JUnit XML: Same Test Reported Twice

The same classname and name appear twice with different outcomes: what a parameterised runner or a merged report can produce. Any store keyed on classname+name overwrites the first result and reports the suite as green or red depending purely on document order.

File: XML · Junit XML · UTF-8
Use case: Error handlingConversion testing+1· Conversion set

JUnit XML: Skip with Message and Body

A skipped case whose reason appears twice, in the message attribute and again as CDATA text inside the <skipped> element. Reporters that read only the attribute silently drop the longer explanation.

File: XML · Junit XML · UTF-8
Use case: Error handlingConversion testing+1· Conversion set

JUnit XML: Timestamp, Hostname and Package Metadata

Every optional run-metadata attribute a JUnit suite may carry (timestamp, hostname, package, id) plus a properties block holding build and branch identifiers. Use it to test that a dashboard reads build context from the report instead of from its own environment.

File: XML · Junit XML · UTF-8
Use case: Metadata testingConversion testing+1· Conversion set

JUnit XML: Truncated Mid-Element (intentionally corrupt)

An intentionally corrupt JUnit report: the file ends in the middle of a testcase attribute value, exactly as it would if the CI worker were killed while the reporter was still writing. Three elements are left unclosed and the document is not well-formed XML. A parser must fail loudly rather than report the two complete cases as the whole run.

File: XML · Corrupt
Use case: Error handlingConversion testing+1· Conversion set

JUnit XML: Vitest Dialect (vitest)

The same 12-case Novus Checkout run written the way vitest 2.0 junit reporter writes it. Vitest names the root suite after the elapsed time and uses the spec file path as classname for every case. All eight dialect files in this group report 12 tests, 1 failure, 1 error and 1 skip, so a JUnit parser can be held to identical totals across every producer.

File: XML · Junit XML · UTF-8
Use case: Conversion testingError handling+1· Conversion set

Jupyter Notebook (IPYNB)

A valid Jupyter notebook (nbformat 4.5) with markdown cells, code cells, and real outputs (stdout stream and an execute result), for testing notebook parsers, nbconvert, and JSON tooling.

File: IPYNB · Notebooks
Use case: JSON parsingConversion testing+1

JWKS (Empty Keys): SAMPLE

Empty JWKS keys array for edge-case JWKS loaders.

File: JSON · Jwks
Use case: JWT / JWKS testingError handling· Conversion set

JWKS (RSA): SAMPLE

SAMPLE JWKS document exposing the Wave G RSA public key for JWT signature verification tests.

File: JSON · Jwks
Use case: JWT / JWKS testing· Conversion set

JWT (HS256 Expired): SAMPLE

SAMPLE HS256 JWT with a past exp claim, for expiry-validation harnesses.

File: JWT · Jwt
Use case: JWT / JWKS testingError handling

JWT (HS256): SAMPLE

SAMPLE JWT with alg=HS256 for auth parsers and algorithm-handling tests. Published sample material only.

File: JWT · Jwt
Use case: JWT / JWKS testing· Conversion set

JWT (HS384): SAMPLE

SAMPLE JWT with alg=HS384 for auth parsers and algorithm-handling tests. Published sample material only.

File: JWT · Jwt
Use case: JWT / JWKS testing· Conversion set

JWT (HS512): SAMPLE

SAMPLE JWT with alg=HS512 for auth parsers and algorithm-handling tests. Published sample material only.

File: JWT · Jwt
Use case: JWT / JWKS testing· Conversion set

JWT (none): SAMPLE

SAMPLE JWT with alg=none for auth parsers and algorithm-handling tests. Published sample material only.

File: JWT · Jwt
Use case: JWT / JWKS testing· Conversion set

JWT (RS256): SAMPLE

SAMPLE JWT with alg=RS256 for auth parsers and algorithm-handling tests. Published sample material only.

File: JWT · Jwt
Use case: JWT / JWKS testing· Conversion set

JWT (RS384): SAMPLE

SAMPLE JWT with alg=RS384 for auth parsers and algorithm-handling tests. Published sample material only.

File: JWT · Jwt
Use case: JWT / JWKS testing· Conversion set

JWT (RS512): SAMPLE

SAMPLE JWT with alg=RS512 for auth parsers and algorithm-handling tests. Published sample material only.

File: JWT · Jwt
Use case: JWT / JWKS testing· Conversion set

JWT Header Claims: RS256 SAMPLE

JWT Header Claims (RS256 SAMPLE) unsigned JSON companion for claim-parser tests (not a live token).

File: JSON · Jwt
Use case: JWT / JWKS testingJSON parsing· Conversion set

JWT Payload: Expired SAMPLE

JWT Payload (Expired SAMPLE) unsigned JSON companion for claim-parser tests (not a live token).

File: JSON · Jwt
Use case: JWT / JWKS testingJSON parsing· Conversion set

JWT: Intentionally Invalid Segments

Intentionally invalid JWT (truncated) for parser error-path tests.

File: JWT · Jwt
Use case: JWT / JWKS testingError handling

Kestrel Bay Territory: CSV with a WKT Geometry Column

Attributes plus a quoted WKT geometry column: the shape PostGIS `COPY`, DuckDB spatial and QGIS delimited-text imports expect. The geometry field contains commas, so it exercises quoted-field parsing as well as geometry decoding.

File: CSV · Territory · 14 records
Use case: GeospatialCSV parsing+1· Conversion set

Kestrel Bay Territory: GML 3.2 Twin (latitude-first)

The territory as GML 3.2 with an EPSG URN srsName. Which means latitude comes first, the opposite of GeoJSON. This is the single most common cause of features landing in the wrong hemisphere, so the file is built to catch it.

File: GML · Territory · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

Explore the test library

Filter the library

5297 results