Novus Examples, Real, documented example files for testing

Semicolon-Delimited CSV

A CSV that uses semicolons as the delimiter (common in European locales), for testing delimiter detection.

File: CSV · CSV · 20 rows
Use case: CSV parsing

Sentiment Classification Dataset (JSONL)

A labelled sentiment-classification dataset in JSON Lines: 24 short product-review-style sentences balanced across positive, negative, and neutral. Fully synthetic; a fixture for testing text-classification loaders, tokenizers, and JSONL parsers.

File: JSONL · Nlp · 24 records
Use case: ML training dataNLP datasets+2

Service Dependency Graph (GraphML, directed)

A directed service-dependency graph in GraphML: ten microservices (web, api, auth, db, cache, queue, worker, …) with their call/dependency edges. A fixture for testing directed-graph importers, cycle detection, and topological sorting.

File: GRAPHML · Graph
Use case: Graph dataData import

Service Dependency Graph: Derived from the Trace Set (json)

The service map you get by aggregating the trace fixtures in this category: five service nodes and the edges between them with call counts and latency percentiles, including the messaging edge that exists only because of a span link. Ground truth for a service-graph processor.

File: JSON · Traces
Use case: ObservabilityGraph data+1

Service Level Agreement (DOCX, SAMPLE)

Fictional SAMPLE service level agreement DOCX twin for contract-template tooling.

File: DOCX · Service Level Agreement
Use case: Templates· Conversion set

Service Level Agreement (PDF, SAMPLE)

PDF twin of the SAMPLE service level agreement.

File: PDF · Service Level Agreement
Use case: TemplatesPDF editor testing· Conversion set

Service Level Objectives: Two SLOs in One Multi-Document YAML (yaml)

Two SLOs (availability and latency) in one multi-document YAML separated by ---, each defined as a ratio of good events to total over a rolling 28-day window. The latency SLO measures the le="1" bucket against the count, which is the correct way to do it from a histogram.

File: YAML · Alerts
Use case: ObservabilityConfig parsing+1· Conversion set

Service Quote Request AcroForm (SAMPLE)

A one-page fillable PDF twin of the service quote request HTML form. Its canonical AcroForm field tree, widgets, values, and appearance streams are generator-validated.

File: PDF · Service Sales · 1 page
Use case: Form testingForm parsing+1· Conversion set

Service Quote Request Field Manifest (JSON)

Machine-readable field names, labels, types, required states, choices, and input hints for the service quote request family.

File: JSON · Service Sales · 8 fields
Use case: Form testingForm parsing+1· Conversion set

Service Quote Request Form (HTML)

A service estimate request for testing lead intake, scope extraction, site classification, schedule normalization, budget bands, and contact-field mapping. This standalone HTML reference works offline, uses explicit labels and native validation, and submits nowhere.

File: HTML · Service Sales · 8 fields
Use case: Form testingForm parsing+1· Conversion set

Service Quote Request Sample Export (CSV)

A one-row UTF-8 CSV export of the fictional service quote request response with columns in the same order as the field manifest.

File: CSV · Service Sales · 1 row
Use case: Form testingForm parsing+1· Conversion set

Service Quote Request Sample Response (JSON)

Fictional submitted values for every documented service quote request field, suitable for request parsing, mapping, and round-trip tests.

File: JSON · Service Sales · 8 fields
Use case: Form testingForm parsing+1· Conversion set

Service Worker (sw.js)

A sample cache-first service worker handling install, activate, and fetch events with an offline fallback, for testing service-worker registration, JS parsers, and PWA tooling.

File: JS · Pwa · JavaScript
Use case: Web assetsSyntax highlighting+1

Service Worker: Offline Shell SAMPLE

Cache-first SAMPLE service worker for PWA offline-shell registration tests.

File: JS · Pwa
Use case: Web assets· Conversion set

Services Agreement Template (DOCX, SAMPLE)

A fictional services agreement DOCX between SAMPLE parties, contract-template tooling fixture.

File: DOCX · Services Agreement
Use case: Templates· Conversion set

Services Agreement Template (PDF, SAMPLE)

PDF twin of the SAMPLE services agreement template.

File: PDF · Services Agreement
Use case: TemplatesPDF editor testing· Conversion set

Severity Scoring and SLA Matrix (CSV)

A severity-band table mapping CVSS ranges to remediation SLAs and gate actions, with the finding count each band has in this fixture set, so a policy engine can be tested end to end. 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: CSV · Vulnerability · 5 rows
Use case: CSV parsingConfig testing+1· Conversion set

Shapefile Bundle: Kestrel Bay Parcels (zipped component set)

A zipped shapefile containing a three-file polygon set with no .cpg, so the DBF encoding is undeclared. Zipping is how shapefiles are actually exchanged, because a bare .shp is meaningless without its sidecars, and it is the upload format most web GIS tools accept.

File: ZIP · Shapefile · 4 members
Use case: GeospatialConversion testing+1· Conversion set

Shapefile Bundle: Kestrel Bay Towns (zipped component set)

A zipped shapefile containing the full five-file point set: .shp, .shx, .dbf, .prj and .cpg. Zipping is how shapefiles are actually exchanged, because a bare .shp is meaningless without its sidecars, and it is the upload format most web GIS tools accept.

File: ZIP · Shapefile · 5 members
Use case: GeospatialConversion testing+1· Conversion set

Shapefile Code Page: ISO-8859-1 Declaration

The sidecar that declares `attributes-cp1252.dbf` as ISO-8859-1. Note that the DBF also carries a language-driver byte in its header, and the two can disagree, which is exactly the ambiguity a reader has to resolve and document.

File: CPG · Shapefile
Use case: GeospatialEncoding detection+1· Conversion set

Shapefile Code Page: UTF-8 Declaration

The sidecar that declares `attributes-utf8.dbf` as UTF-8. Note that the DBF also carries a language-driver byte in its header, and the two can disagree, which is exactly the ambiguity a reader has to resolve and document.

File: CPG · Shapefile
Use case: GeospatialEncoding detection+1· Conversion set

Shapefile DBF: Accented Attributes in CP1252

The same four accented attribute rows written in CP1252. Both files are exactly the same size because DBF fields are fixed-width in bytes, not characters, so the UTF-8 table fits fewer characters per field, and a reader that guesses the encoding produces mojibake rather than an obvious failure.

File: DBF · Shapefile · 4 records
Use case: GeospatialEncoding detection+1· Conversion set

Shapefile DBF: Accented Attributes in UTF-8

The same four accented attribute rows written in UTF-8. Both files are exactly the same size because DBF fields are fixed-width in bytes, not characters, so the UTF-8 table fits fewer characters per field, and a reader that guesses the encoding produces mojibake rather than an obvious failure.

File: DBF · Shapefile · 4 records
Use case: GeospatialEncoding detection+1· Conversion set

Shapefile: Code Page Sidecar (.cpg, UTF-8)

A one-line sidecar naming the encoding of the .dbf. Without it a reader has to guess (usually cp1252), and every non-ASCII attribute value comes back as mojibake, which is the single most common shapefile data-loss bug.

File: CPG · Shapefile
Use case: GeospatialEncoding detection+1· Conversion set

Explore the test library

Filter the library

5297 results