Novus Examples, Real, documented example files for testing

Copper Oven Bakery: Equivalent purchase import TSV

Equivalent purchase import TSV for Copper Oven Bakery. 96 data rows, 8 columns and 96 expected accepted rows.

File: TSV · Business Kits · 96 rows
Use case: Data import

Copper Oven Bakery: Guest review import CSV

Guest review import CSV for Copper Oven Bakery. 18 data rows, 5 columns and 18 expected accepted rows.

File: CSV · Business Kits · 18 rows
Use case: Data import

Copper Oven Bakery: Intentionally invalid purchase import

Intentionally invalid purchase import for Copper Oven Bakery. 4 data rows, 8 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Copper Oven Bakery: Intentionally invalid review import

Intentionally invalid review import for Copper Oven Bakery. 4 data rows, 5 columns and 0 expected accepted rows.

File: CSV · Business Kits · 4 rows
Use case: Data importError handling

Copper Oven Bakery: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Copper Oven Bakery. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

File: JSON · Business Kits
Use case: Data importError handling

Copper Oven Bakery: Linked operating model

Linked operating model for Copper Oven Bakery. 368 records across 18 linked tables; no duplicate primary keys or missing references. Supplier spend=10,172.83 CAD; Net menu sales=6,651.14 CAD; Menu items sold=1,316.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits · 368 records
Use case: Data import

Copper Oven Bakery: Numeric expected results

Numeric expected results for Copper Oven Bakery. Exact table counts, metric formulas, 8 chart points and three negative-test outcomes. Supplier spend=10,172.83 CAD; Net menu sales=6,651.14 CAD; Menu items sold=1,316.00 items; Guest reviews=18.00 records.

File: JSON · Business Kits
Use case: Data import

Copper Oven Bakery: Operating chart PNG

Operating chart PNG for Copper Oven Bakery. A 1440 by 900 RGB chart with 8 labeled source-derived observations in CAD.

File: PNG · Business Kits · 1440 × 900 px
Use case: Data import

Copper Oven Bakery: Operating model JSON Schema

Operating model JSON Schema for Copper Oven Bakery. Draft 2020-12 schema accepts the paired operating model. Relational rules additionally require unique keys and existing foreign references.

File: JSON · Business Kits
Use case: Data import

Copper Oven Bakery: Operating report PDF

Operating report PDF for Copper Oven Bakery. Three readable pages summarize the same model, chart, source tables and usage instructions. Supplier spend=10,172.83 CAD; Net menu sales=6,651.14 CAD; Menu items sold=1,316.00 items; Guest reviews=18.00 records.

File: PDF · Business Kits · 3 pages
Use case: Data import

Copper Oven Bakery: Purchase import CSV

Purchase import CSV for Copper Oven Bakery. 96 data rows, 8 columns and 96 expected accepted rows.

File: CSV · Business Kits · 96 rows
Use case: Data import

Copper Oven Bakery: Workflow and import guide

Workflow and import guide for Copper Oven Bakery. Documents 18 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Corrected gettext MO: Deutsch

GNU gettext loads all seven original translations using the declared UTF-8 charset. Message IDs are sorted, metadata occupies the empty key, Unicode survives, and the %s placeholder is retained. The corrected catalog preserves the legacy translations.

File: MO · Gettext Corrected
Use case: Internationalization

Corrected gettext MO: Français

GNU gettext loads all seven original translations using the declared UTF-8 charset. Message IDs are sorted, metadata occupies the empty key, Unicode survives, and the %s placeholder is retained. The corrected catalog preserves the legacy translations.

File: MO · Gettext Corrected
Use case: Internationalization

Corrected gettext MO: Português brasileiro

GNU gettext loads all seven original translations using the declared UTF-8 charset. Message IDs are sorted, metadata occupies the empty key, Unicode survives, and the %s placeholder is retained. The corrected catalog preserves the legacy translations.

File: MO · Gettext Corrected
Use case: Internationalization

Corrected gettext MO: 한국어

GNU gettext loads all seven original translations using the declared UTF-8 charset. Message IDs are sorted, metadata occupies the empty key, Unicode survives, and the %s placeholder is retained. The corrected catalog preserves the legacy translations.

File: MO · Gettext Corrected
Use case: Internationalization

CORS Misconfigured Headers: SAMPLE

Intentionally misconfigured CORS SAMPLE (* + credentials) for policy linters.

File: HEADERS · Headers
Use case: API testingError handling

CORS Response Headers: SAMPLE

SAMPLE CORS response header block as plain text for header parsers and policy tests.

File: HEADERS · Headers
Use case: API testing

Cosine Similarity Pairs (JSONL)

Precomputed cosine similarity pairs for embedding eval scripts.

File: JSONL · Embeddings · 6 records
Use case: Model evaluation

Countdown with Timecode (MP4)

A six-second countdown (5→0) with a sweeping second-arc, a burned-in SS:FF timecode, and a beep on each second: a slate/leader fixture for testing timecode reading, frame-accurate seeking, and sync.

File: MP4 · Test Patterns · 480x270
Use case: Conversion testing

Cover Letter Template (DOCX)

A neutral cover-letter template with a standard structure you can adapt to any role.

File: DOCX · Cover Letter
Use case: Templates

Coverage, LCOV with Several TN: Test Names

Three named test runs in one tracefile, each covering a different part of the tree, reported via the TN: record most tools quietly discard. Keeping the name is what lets a report answer which suite covered a given line.

File: LCOV · Coverage · 4 records
Use case: Conversion testingCode parsing+1· Conversion set

Coverage: Clover XML

The Clover serialisation, whose <metrics> element rolls statements, conditionals and methods into a single elements/coveredelements pair. Anything reading only that pair reports a blended percentage that matches none of the other three formats unless the components are separated first. Every file in this group describes the same four-file source tree and reports 127/140 lines, 17/24 branch outcomes and 18/20 functions, so a converter can be diffed against a known answer.

File: XML · Coverage
Use case: Conversion testingCode parsing+1· Conversion set

Coverage: Cobertura at Zero Coverage

A structurally complete Cobertura report in which line-rate and branch-rate are 0.0 everywhere. The counterpart to the zero-coverage LCOV file, for checking that a converter keeps the class and method structure when there is nothing covered to describe.

File: XML · Coverage
Use case: Conversion testingCode parsing+1· Conversion set

Explore the test library

Filter the library

5297 results

Copper Oven Bakery: Equivalent purchase import TSV

Copper Oven Bakery: Guest review import CSV

Copper Oven Bakery: Intentionally invalid purchase import

Copper Oven Bakery: Intentionally invalid review import

Copper Oven Bakery: Intentionally invalid semantic test records

Copper Oven Bakery: Linked operating model

Copper Oven Bakery: Numeric expected results

Copper Oven Bakery: Operating chart PNG

Copper Oven Bakery: Operating model JSON Schema

Copper Oven Bakery: Operating report PDF

Copper Oven Bakery: Purchase import CSV

Copper Oven Bakery: Workflow and import guide

Corrected gettext MO: Deutsch

Corrected gettext MO: Français

Corrected gettext MO: Português brasileiro

Corrected gettext MO: 한국어

CORS Misconfigured Headers: SAMPLE

CORS Response Headers: SAMPLE

Cosine Similarity Pairs (JSONL)

Countdown with Timecode (MP4)

Cover Letter Template (DOCX)

Coverage, LCOV with Several TN: Test Names

Coverage: Clover XML

Coverage: Cobertura at Zero Coverage

Filter the library