Novus Examples, Real, documented example files for testing

Pine Assembly Workshop: Operating chart PNG

Operating chart PNG for Pine Assembly Workshop. A 1440 by 900 RGB chart with 6 labeled source-derived observations in units.

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

Pine Assembly Workshop: Operating model JSON Schema

Operating model JSON Schema for Pine Assembly Workshop. 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

Pine Assembly Workshop: Operating report PDF

Operating report PDF for Pine Assembly Workshop. Three readable pages summarize the same model, chart, source tables and usage instructions. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

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

Pine Assembly Workshop: Workflow and import guide

Workflow and import guide for Pine Assembly Workshop. Documents 11 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Pine Property Services: Blank input table templates

Blank input table templates for Pine Property Services. 6 header-only CSV templates and one setup guide. No filled sample records or executable content.

File: ZIP · Business Kits
Use case: Data import

Pine Property Services: Editable operating workbook

Editable operating workbook for Pine Property Services. Native sheets preserve 57 source records, 3 calculated headline metrics and one editable chart. Estimated work=3,858.00 USD; Recorded job costs=2,838.00 USD; Work orders=12.00 records.

File: XLSX · Business Kits
Use case: Data import

Pine Property Services: Generic primary records CSV

Generic primary records CSV for Pine Property Services. 6 generic records with stable primary keys. Map the documented fields before importing into another platform.

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

Pine Property Services: Intentionally invalid semantic test records

Intentionally invalid semantic test records for Pine Property Services. 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

Pine Property Services: Linked operating model

Linked operating model for Pine Property Services. 57 records across 6 linked tables; no duplicate primary keys or missing references. Estimated work=3,858.00 USD; Recorded job costs=2,838.00 USD; Work orders=12.00 records.

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

Pine Property Services: Numeric expected results

Numeric expected results for Pine Property Services. Exact table counts, metric formulas, 12 chart points and three negative-test outcomes. Estimated work=3,858.00 USD; Recorded job costs=2,838.00 USD; Work orders=12.00 records.

File: JSON · Business Kits
Use case: Data import

Pine Property Services: Operating chart PNG

Operating chart PNG for Pine Property Services. A 1440 by 900 RGB chart with 12 labeled source-derived observations in USD.

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

Pine Property Services: Operating model JSON Schema

Operating model JSON Schema for Pine Property Services. 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

Pine Property Services: Operating report PDF

Operating report PDF for Pine Property Services. Three readable pages summarize the same model, chart, source tables and usage instructions. Estimated work=3,858.00 USD; Recorded job costs=2,838.00 USD; Work orders=12.00 records.

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

Pine Property Services: Workflow and import guide

Workflow and import guide for Pine Property Services. Documents 6 source tables, exact expected totals and supported versus manual workflows.

File: MD · Business Kits
Use case: Data import

Pink Noise

Three seconds of pink noise with a 1/f power spectrum: the standard reference for loudness and room-calibration testing.

File: WAV · Reference Tones · 3 s
Use case: Audio analysis

pip constraints.txt

A pip constraints file pinning the same nine fictional packages. Constraints bound a resolution without adding dependencies, so a tool that treats this like requirements.txt installs nine packages too many. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: TXT · Lockfiles
Use case: Config parsingConversion testing· Conversion set

pip requirements.txt With Pinned Hashes

A hash-pinned pip requirements file with two sha256 hashes per fictional package (wheel and sdist) and line continuations: the form `--require-hashes` installs demand. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: TXT · Lockfiles
Use case: Config parsingConversion testing+1· Conversion set

pip-audit Report (JSON)

A pip-audit report for the fictional Python packages. It deliberately carries no severity field (pip-audit does not assign one), which is the case a severity gate must handle without defaulting to critical. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

File: JSON · Vulnerability
Use case: JSON parsingConversion testing+1· Conversion set

pip-compile Annotated requirements.txt

A pip-compile output where every pin carries a `# via` annotation naming the requirement that pulled it in: the only place the transitive graph survives in a pip workflow. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: TXT · Lockfiles
Use case: Config parsingGraph data+1· Conversion set

pipdeptree JSON Output

pipdeptree output, whose top level is an ARRAY rather than an object (the shape that breaks a loader written against npm's tree) with both installed and required versions on every edge. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: JSON · Graphs
Use case: JSON parsingGraph data+1· Conversion set

Pipeline DAG Topology (JSON, with Expected Answers)

The shared six-task topology as a plain node/edge JSON document that also publishes the expected answers (roots, leaves, longest path, and topological order), so a graph library or DAG visualiser can be scored without a hand-written oracle.

File: JSON · Airflow
Use case: Graph dataData engineering+1· Conversion set

Pipeline DAG with a Cycle (JSON), Intentionally Invalid

The shared topology plus one back edge, making it intentionally invalid as a DAG. The document publishes the cycle it contains, so a scheduler or graph validator can be tested on both detecting the cycle and naming it.

File: JSON · Airflow
Use case: Error handlingConfig parsing+1

Pipfile.lock (Pipenv)

A Pipenv lockfile in JSON, with the _meta hash that ties it to its Pipfile, a named index source and nine fictional pinned packages in the default section. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: LOCK · Lockfiles
Use case: JSON parsingConfig parsing+1· Conversion set

Pitch Deck (ODP, SAMPLE)

OpenDocument twin of the SAMPLE pitch deck for ODP converters.

File: ODP · Pitch · 5 slides
Use case: TemplatesConversion testing· Conversion set

Explore the test library

Filter the library

5297 results