Novus Examples, Real, documented example files for testing

Sample-Rate Set: 440 Hz @ 8000 Hz

Same 440 Hz tone rendered at 8000 Hz sample rate: twin in the 8k/16k/44.1k set.

File: WAV · Sample Rate Set · 0.6 s
Use case: Audio analysisConversion testing· Conversion set

Sample-Rate Set: 880 Hz @ 16000 Hz

880 Hz tone at 16000 Hz: second ladder for resampling QA.

File: WAV · Sample Rate Set · 0.5 s
Use case: Audio analysisConversion testing· Conversion set

Sample-Rate Set: 880 Hz @ 44100 Hz

880 Hz tone at 44100 Hz: second ladder for resampling QA.

File: WAV · Sample Rate Set · 0.5 s
Use case: Audio analysisConversion testing· Conversion set

Sample-Rate Set: 880 Hz @ 8000 Hz

880 Hz tone at 8000 Hz: second ladder for resampling QA.

File: WAV · Sample Rate Set · 0.5 s
Use case: Audio analysisConversion testing· Conversion set

SBOM Attestation Envelope (cosign Shape)

An attestation that binds an SBOM to an artifact digest rather than shipping the SBOM loose: the pattern keyless signing produces, complete with the empty keyid that identity-based signing leaves behind. Signatures, key ids and certificates here are SAMPLE placeholders: the base64 decodes to the words 'SAMPLE SIGNATURE', so verification must fail. Nothing here is cryptographically valid and no key material is real.

File: JSON · Provenance
Use case: JSON parsingSchema validation+1· Conversion set

SBOM Component Inventory (CSV)

The same fictional component tree flattened to a spreadsheet-friendly CSV (name, version, licence, depth, purl and a SHA-256 prefix) for testing the export path SBOM tools offer alongside JSON. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: CSV · Sbom · 10 rows
Use case: CSV parsingData import+1· Conversion set

SBOM Format Crosswalk (CycloneDX to SPDX)

The field-by-field map between the CycloneDX 1.6 and SPDX 2.3 documents in this category, plus the five invariants a correct conversion preserves and the three things it legitimately loses. Every package, version, hash and licence is fictional: the tree describes nothing real.

File: MD · Sbom
Use case: Conversion testingEditor testing· Conversion set

SBV Captions (YouTube)

A YouTube SBV caption file (start,end timestamp lines followed by caption text) carrying the same three captions, for testing SBV parsers and YouTube caption import.

File: SBV · Subtitles · 3 cues
Use case: Subtitle parsingConversion testing+1· Conversion set

SBV: YouTube Timing Without Cue Indices

SubViewer/SBV as YouTube exports it: no cue indices, a comma rather than an arrow between start and end, and single-digit hours. Superficially similar enough to SubRip that format detection by eye fails, which makes it a good test of sniffing logic: a parser that guesses SubRip from the timestamps then trips on the missing index.

File: SBV · Captions Edge · 4 cues
Use case: Subtitle parsingVideo QA· Conversion set

Scala Fold

Scala foldLeft snippet for syntax and indexer tests.

File: SCALA · Scala
Use case: Syntax highlightingCode parsing+1

Scala Hello

Scala 3-style object hello for Scalac / Metals fixtures.

File: SCALA · Scala
Use case: Syntax highlightingCode parsing+1

Scala Match

Scala pattern match SAMPLE for Metals fixtures.

File: SCALA · Scala
Use case: Syntax highlightingCode parsing+1

Scan: Interlaced, Bottom Field First

The same interlacing with the opposite field order, the DV and SD convention. Deinterlacing with the wrong field order makes motion jitter backwards: a subtle, very common bug that this pair makes reproducible. In Matroska rather than MP4 so the catalog renders a poster instead of advertising an inline player, combing artefacts are best judged from a still anyway.

File: MKV · Scan · 480x270
Use case: Video codecsConversion testing+1· Conversion set

Scan: Interlaced, Top Field First

Alternate lines carry alternate instants, with the top field displayed first: the HD broadcast convention. Shown progressively it combs on every moving edge. In Matroska rather than MP4 so the catalog renders a poster instead of advertising an inline player, combing artefacts are best judged from a still anyway.

File: MKV · Scan · 480x270
Use case: Video codecsConversion testing+1· Conversion set

Scan: Progressive

Whole frames, captured and displayed at once: the reference for this group and how essentially all modern video is shot. In Matroska rather than MP4 so the catalog renders a poster instead of advertising an inline player, combing artefacts are best judged from a still anyway.

File: MKV · Scan · 480x270
Use case: Video codecsConversion testing+1· Conversion set

Scanner Report, Truncated: Intentionally Corrupt

An intentionally corrupt scanner report: a valid Trivy-shaped JSON document cut off inside the first finding, for testing that a CI gate fails the build rather than reporting zero vulnerabilities. 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: Error handlingJSON parsing· Conversion set

Scanner SARIF 2.1.0 Report

The same four SAMPLE findings expressed as SARIF 2.1.0 (the format code-scanning dashboards ingest) with a rules array, security-severity properties and physical locations. 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

Scatter Plot (PNG)

A scatter plot of 120 seeded points (order value versus items per order) showing a positive correlation, with labelled axes, for testing point-cloud extraction and chart parsing.

File: PNG · Charts
Use case: Chart recognitionThumbnail generation· Conversion set

SCC, Intentionally Corrupt: Wrong Parity Bytes

An intentionally corrupt SCC file whose first caption is valid but whose second carries byte pairs with the wrong parity. CEA-608 requires odd parity in bit 7 of every byte, and broadcast decoders use it to detect transmission errors. Tests whether a decoder checks parity at all, and whether it drops just the bad caption or the whole file.

File: SCC · Captions Corrupt
Use case: Subtitle parsingVideo QA· Conversion set

SCC: Broadcast CEA-608 Captions

Broadcast closed captions as Scenarist SCC: SMPTE timecodes followed by hexadecimal CEA-608 byte pairs, with odd parity set on every byte as the standard requires. Uses pop-on mode: RCL to load, ENM to clear non-displayed memory, a preamble address code for row 15, the character pairs, then EOC to display. This is the fixture that exposes decoders which treat captions as text: the parity bits, the two-byte control codes and the frame-accurate timecodes all have to be handled.

File: SCC · Captions Formats
Use case: Subtitle parsingCaption encoding+2· Conversion set

SCTE-35: Splice Insert (Break End / Return to Network)

The matching return cue for the break-start splice_insert in this group: the same spliceEventId with outOfNetworkIndicator false, signalling the feed is coming back from the ad break. It carries no BreakDuration because the return is explicit rather than automatic. Pairing start and end cues by event id is exactly what an ad-insertion implementation has to get right, and this is the pair to test it on.

File: XML · Ad Signalling
Use case: Ad insertionStreaming manifests+1· Conversion set

SCTE-35: Splice Insert (Break Start)

An SCTE-35 splice_insert as XML: the cue that tells a downstream packager a linear ad break starts. outOfNetworkIndicator marks entry into the break, ptsTime is 8 seconds on the 90 kHz PTS clock, and the 30-second break auto-returns. This is the signal a manifest manipulator converts into an HLS EXT-X-CUE-OUT or a new DASH period.

File: XML · Ad Signalling
Use case: Ad insertionStreaming manifests+1· Conversion set

SCTE-35: Time Signal With Segmentation Descriptor

The modern SCTE-35 form: a time_signal command carrying a segmentation descriptor rather than a bare splice_insert. Type 34 marks a provider placement opportunity start, and the delivery restrictions declare that this break may not be filled for web delivery: the field that ad-insertion logic is supposed to honour and frequently ignores. Includes a base64 UPID identifying the content.

File: XML · Ad Signalling · 2700000 (30.0s)
Use case: Ad insertionStreaming manifests+1· Conversion set

Security Contact JSON: 01

Well-known security contact JSON SAMPLE #1.

File: JSON · Well Known
Use case: Web assets

Explore the test library

Filter the library

5297 results