Novus Examples, Real, documented example files for testing

Fintech Transaction History (CSV)

Synthetic bank transaction history for personal-finance importer tests.

File: CSV · Fintech · 2 rows
Use case: Data importCSV parsing

FITS BINTABLE: Typed Columns with TUNIT (.fits)

A FITS binary table with four typed columns, big-endian numerics packed with no inter-field padding and TUNIT declaring milli-jansky on the two flux columns. It is the fixture for a table reader that has to build a row struct from TFORM codes rather than guess widths.

File: FITS · Fits · 12 rows
Use case: Scientific dataSerialization testing+1· Conversion set

FITS BLANK: Undefined Integer Pixels (.fits)

Integer FITS images mark undefined pixels with the BLANK keyword, and BLANK is compared against the stored value before BZERO and BSCALE are applied. Scale first and the four undefined pixels turn into a perfectly plausible zero, which is the ordering bug this file exists to expose.

File: FITS · Fits
Use case: Scientific dataSerialization testing+1· Conversion set

FITS Header-Only: Valid File With No Pixels (.fits)

A completely valid FITS file consisting of one 2880-byte header block and no data unit, which the standard permits whenever NAXIS is 0. It separates readers that model the data array as optional from readers that treat 'no pixels' as corruption.

File: FITS · Fits
Use case: Scientific dataSerialization testing+1· Conversion set

FITS Image (.fits)

A minimal but valid FITS image (a primary header of 80-character cards padded to a 2880-byte block, followed by a 16x16 unsigned-byte pixel gradient) for testing FITS readers and header-card parsers.

File: FITS · Scientific
Use case: Scientific data

FITS Image: BITPIX 16 with BZERO Unsigned Trick (.fits)

FITS has no unsigned 16-bit type, so unsigned data is stored signed with BZERO = 32768 and recovered as BZERO + BSCALE * stored. Every stored value in this image is negative, so a reader that ignores the scaling returns an entirely negative frame while parsing the file perfectly.

File: FITS · Fits
Use case: Scientific dataSerialization testing· Conversion set

FITS Image: BITPIX 8 Unsigned Bytes (.fits)

The baseline rung of the BITPIX ladder: a 24x16 synthetic star field stored as unsigned bytes, the one integer width FITS holds without a BZERO shift. Every image in this family carries the same scene so a decoder can be scored across data types.

File: FITS · Fits
Use case: Scientific dataSerialization testing· Conversion set

FITS Image: float32 with NaN and Inf Pixels (.fits)

Single-precision FITS pixels including two NaNs, which is the only way the standard marks undefined data for floating BITPIX, plus one +Inf. Statistics computed without NaN-aware reductions come back as NaN for the entire frame.

File: FITS · Fits
Use case: Scientific dataSerialization testing+1· Conversion set

FITS Image: float64 Double Precision (.fits)

The top rung of the BITPIX ladder, carrying the identical synthetic scene as IEEE-754 doubles with DATAMIN and DATAMAX declared. It is the reference against which the 8-, 16- and 32-bit members of the family are scored for precision loss.

File: FITS · Fits
Use case: Scientific dataSerialization testing· Conversion set

FITS Long Header: Cards Across Several 2880-Byte Blocks (.fits)

A header of 47 cards, so END lands well past the first 2880-byte block, alongside repeated HISTORY and COMMENT cards that legally share a keyword. A parser that reads one block and stops never sees END and truncates the metadata.

File: FITS · Fits
Use case: Scientific dataSerialization testing· Conversion set

FITS Multi-Extension: Empty Primary plus SCI and MASK (.fits)

A three-HDU FITS file whose primary unit is header-only (NAXIS = 0) with the real data in named SCI and MASK extensions. A reader that only ever looks at HDU 0 reports an empty file, which is exactly the bug this fixture is built to catch.

File: FITS · Fits
Use case: Scientific dataSerialization testing· Conversion set

FITS WCS Header Cards: CSV Reference (.csv)

Every header card of the tangent-plane WCS file transcribed to keyword, value and comment columns. Diff a header parser's output against it to prove the parser split each 80-column card at the right places instead of guessing on whitespace.

File: CSV · Fits
Use case: Scientific dataConversion testing+1· Conversion set

FITS with World Coordinate System: Tangent Plane (.fits)

A 32-bit integer image carrying a complete tangent-plane WCS: 1-based CRPIX reference pixels, a deliberately negative CDELT1 so right ascension runs the other way, and an ICRS frame. It targets the two mistakes every WCS implementation makes first, the 1-based origin and the flipped axis.

File: FITS · Fits
Use case: Scientific dataSerialization testing+1· Conversion set

Fixed-Width Positions File (TXT)

A classic fixed-width text extract with documented column positions, for COBOL-style / mainframe importer tests.

File: TXT · Encodings · 3 rows
Use case: CSV parsingData import+1

FLAC with Metadata Stripped

The matching FLAC reduced to STREAMINFO and the exact same audio frames, so metadata-removal tests can compare compressed essence byte for byte.

File: FLAC · Tagged
Use case: Metadata testingConversion testing· Paired fixture

FLAC with Vorbis Comments and Picture

A FLAC whose STREAMINFO and audio frames are accompanied by known Vorbis comments and a 32-pixel PNG front cover.

File: FLAC · Tagged
Use case: Metadata testingConversion testing· Paired fixture

FLAC: Lossless

The clip as FLAC: free lossless audio compression. Byte-for-byte recoverable to the source PCM; for testing lossless decoders and conversion.

File: FLAC · Codec Set · FLAC
Use case: Conversion testingAudio analysis· Conversion set

Flaky Detection: 40-Build Test-Run History (JSONL)

Forty builds of six tests, one JSON object per line, with three tests that fail intermittently and three that never do. This is the input shape a flake detector ingests; the CSV twin in this group holds the aggregate it should produce.

File: JSONL · Flaky Runs · 240 records
Use case: JSON parsingTime-series data+1· Conversion set

Flaky Detection: Per-Test Failure-Rate Summary (CSV)

The aggregate answer key for the 40-build history in this group: runs, passes, failures and failure rate per test, with each test labelled stable or flaky. Use it to score a detector rather than eyeballing 240 JSONL records.

File: CSV · Flaky Runs · 6 rows
Use case: CSV parsingConversion testing+1· Conversion set

Flaky Run: Network Dependency, Build #301 (errored)

Build #301 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is errored while the other five cases pass every time. The underlying cause is a real call to the fictional payments host instead of the stub. Read the whole family in build order to reproduce what a flake detector sees.

File: XML · Flaky Runs
Use case: Error handlingLog parsing+1· Conversion set

Flaky Run: Network Dependency, Build #302 (passing)

Build #302 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is passing while the other five cases pass every time. The underlying cause is a real call to the fictional payments host instead of the stub. Read the whole family in build order to reproduce what a flake detector sees.

File: XML · Flaky Runs
Use case: Error handlingLog parsing+1· Conversion set

Flaky Run: Network Dependency, Build #303 (passing)

Build #303 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is passing while the other five cases pass every time. The underlying cause is a real call to the fictional payments host instead of the stub. Read the whole family in build order to reproduce what a flake detector sees.

File: XML · Flaky Runs
Use case: Error handlingLog parsing+1· Conversion set

Flaky Run: Network Dependency, Build #304 (passing)

Build #304 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is passing while the other five cases pass every time. The underlying cause is a real call to the fictional payments host instead of the stub. Read the whole family in build order to reproduce what a flake detector sees.

File: XML · Flaky Runs
Use case: Error handlingLog parsing+1· Conversion set

Flaky Run: Network Dependency, Build #305 (errored)

Build #305 of five consecutive runs of checkout.PaymentTest, in which capturesAuthorisedPayment is errored while the other five cases pass every time. The underlying cause is a real call to the fictional payments host instead of the stub. Read the whole family in build order to reproduce what a flake detector sees.

File: XML · Flaky Runs
Use case: Error handlingLog parsing+1· Conversion set

Explore the test library

Filter the library

5297 results