Novus Examples, Real, documented example files for testing

Tool Function JSON Schema

JSON Schema for a sample weather tool's parameters.

File: JSON · Nlp
Use case: Tool calling / function callingSchema / OpenAPI testing

Tool-calling Mini Trace (JSONL)

Minimal single-turn tool-calling trace for quick parser smoke tests.

File: JSONL · Nlp · 1 record
Use case: Tool calling / function calling

Tool-calling Traces: Anthropic Format (JSONL)

Anthropic-style tool_use blocks with paired tool results for agent harness tests.

File: JSONL · Nlp · 6 records
Use case: Tool calling / function callingML training data

Tool-calling Traces: OpenAI Format (JSONL)

OpenAI-style tool-call JSONL with function invocation and tool result messages.

File: JSONL · Nlp · 6 records
Use case: Tool calling / function callingML training data+1

TopoJSON, Intentionally Invalid: Arc Referenced Without Reversal

Intentionally invalid: East Field references the shared arc forwards when it should use the reversed form, so its ring no longer closes. This is the single most common hand-editing mistake in TopoJSON, and it produces a plausible-looking file that renders as a torn shape.

File: TOPOJSON · Topojson · UTF-8
Use case: GeospatialError handling+1· Conversion set

TopoJSON: Coarse 100-Step Quantization (visible rounding)

The same territory quantized to only 100 steps, so rounding error reaches roughly 220 m and several vertices collapse onto the same grid cell. Use it to prove that a tolerance in your comparison code is actually being applied rather than accidentally passing.

File: TOPOJSON · Topojson · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

TopoJSON: Decoded GeoJSON Reference for the Shared-Arc File

Exactly what the shared-arc topology decodes to: two polygons whose rings are stitched from arcs 0, 1 and 2 with arc 0 reversed for the eastern parcel. Because that file is unquantized, this comparison is exact rather than tolerance-based.

File: GEOJSON · Topojson · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

TopoJSON: Geometry Ids Alongside Properties

Five town geometries that each carry both an `id` member and a `properties` object. TopoJSON keeps these separate, and converters that fold the id into properties (or drop it) break joins against an external attribute table.

File: TOPOJSON · Topojson · UTF-8
Use case: GeospatialJSON parsing+1· Conversion set

TopoJSON: Quantized to a 10,000-Step Grid

The full territory quantized onto a 10,000-step grid with a transform block and delta-encoded arc positions: the default TopoJSON encoding. Rounding is bounded by the grid spacing, which over this 0.28-degree extent is about 2.2 m.

File: TOPOJSON · Topojson · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

TopoJSON: Three Named Objects in One Topology

One topology carrying three separately named objects (towns, roads and areas) that all index into the same arc pool. This is how a single TopoJSON file ships what would otherwise be three layers, and readers that assume exactly one object silently show only the first.

File: TOPOJSON · Topojson · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

TopoJSON: Two Parcels Sharing One Arc

Two adjacent parcels that share their common boundary as a single arc: West Field references it as 0 and East Field as ~0, the negative-index form that means traverse it backwards. Storing the boundary once is the whole point of TopoJSON, and it is also where naive decoders produce gaps or slivers.

File: TOPOJSON · Topojson · UTF-8
Use case: GeospatialConversion testing+1· Conversion set

TopoJSON: Zero-Length Arc

A topology whose fourth arc repeats the same position twice, giving a line of zero length. Quantization produces these routinely when two vertices land in the same grid cell, and simplification code that divides by segment length fails on them.

File: TOPOJSON · Topojson · UTF-8
Use case: GeospatialError handling+1· Conversion set

Trace Span Table: Flat CSV Export (csv)

The same 13 spans flattened to a CSV table: span and parent IDs, service, name, kind, start timestamp, duration and status. The shape a trace store exports for spreadsheet analysis, and a readable ground truth to diff the three JSON twins against.

File: CSV · Traces · 13 rows
Use case: ObservabilityCSV parsing+1· Conversion set

traffic-advice.json (private prefetch proxy opt-in)

A traffic-advice document opting a fictional origin into private prefetch proxy traffic at full fraction while disallowing every other agent. For testing prefetch-proxy discovery and the JSON-array (not object) top level this format uses.

File: JSON · Well Known
Use case: Web assetsJSON parsing+1· Conversion set

Trailing Silence 1s: 440 Hz Tone

A 440 Hz tone followed by exactly 1 second of digital silence. The tone should end at 2.0s: a direct fixture for testing trailing-silence trimming.

File: WAV · Silence Trim Set · 44100 Hz
Use case: Auto-trim testingAudio analysis

Trailing Silence 3s: 440 Hz Tone

A 440 Hz tone followed by exactly 3 seconds of digital silence. The tone should end at 2.0s: a direct fixture for testing trailing-silence trimming.

File: WAV · Silence Trim Set · 44100 Hz
Use case: Auto-trim testingAudio analysis

Trailing Silence 5s: 440 Hz Tone

A 440 Hz tone followed by exactly 5 seconds of digital silence. The tone should end at 2.0s: a direct fixture for testing trailing-silence trimming.

File: WAV · Silence Trim Set · 44100 Hz
Use case: Auto-trim testingAudio analysis

Transitive Dependency Closure (CSV)

Every edge in the fictional dependency graph as one row (parent, child, declared range, resolved version, depth and whether the edge is direct), the form a spreadsheet or SQL import can aggregate. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: CSV · Graphs · 10 rows
Use case: CSV parsingGraph data+1· Conversion set

Travel Itinerary Template (DOCX)

A day-by-day travel itinerary with timed entries for a three-day trip and a notes section for confirmations: a realistic planning document you can adapt.

File: DOCX · Itinerary
Use case: Templates

Trivy Clean Scan Report (Zero Findings)

A clean scan report: the case dashboards get wrong. Trivy omits the Vulnerabilities key entirely rather than emitting an empty array, so a reader that assumes the key exists throws on a passing build. 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 parsingError handling+1· Conversion set

Trivy Container Image Scan Report (JSON)

A Trivy-shaped image report with three result blocks (OS packages, language packages and a Dockerfile misconfiguration), so a parser must handle a Results array whose members have different keys. 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 parsingSchema validation+1· Conversion set

Trivy Filesystem Scan Report (JSON)

A Trivy-shaped filesystem scan report with four SAMPLE findings against a fictional npm lockfile, one per severity band, each with a CVSS v3.1 vector, CWE class and fixed version. 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 parsingSchema validation+1· Conversion set

TS: MPEG-TS H.264 Clip

The clip as an MPEG transport stream (.ts): the container behind HLS streaming and broadcast. For testing TS demuxing and HLS tooling.

File: TS · Ts · 480x270
Use case: Conversion testing

TTC: Collection of Two Variable Fonts

A collection whose members are themselves variable fonts, each with its own axis, fvar, gvar and STAT. The case that breaks loaders which handle collections or variations but never both at once. Original typeface, free to use.

File: TTC · Collection
Use case: Conversion testingMetadata testing· Conversion set

Explore the test library

Filter the library

5297 results