Explore the test library

Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.

Filter the library

SearchTypeCategorySubcategoryFormatUse caseIndustryWorkflowValidityEditable workspaceDestination platformBrowser test targetSort

5297 results

Page 156 of 221; 24 results per page.

Show the canonical directory

Quiet Audio Needing Normalization

A very quiet modulated tone (~peak 0.04) for testing loudness normalization and gain staging.

File: WAV · Signals · 1.5 s
Use case: Audio analysis

R Data Frame

R data.frame construction: realistic snippet for R parsers.

File: R · R
Use case: Syntax highlightingCode parsing+1

R Hello

Minimal R hello-world for RStudio / language-server fixtures.

File: R · R
Use case: Syntax highlightingCode parsing+1

R Pipe

R native pipe (|>) snippet for modern R tooling.

File: R · R
Use case: Syntax highlightingCode parsing+1

R: Intentionally Invalid

Intentionally invalid R (unclosed call) for parser tests.

File: R · R
Use case: Error handlingCode parsing+1

Ranking Eval Queries (JSONL)

Short query list for ranking benchmark harness smoke tests.

File: JSONL · Eval · 6 records
Use case: Model evaluationJSON parsing

Raw float64 Block: Big-Endian, No Header (.bin)

The same sixteen doubles written in network byte order, so every eight-byte group is the mirror of the little-endian twin. Decoding it with the wrong assumption produces small plausible-looking numbers rather than an error, which is why this pair exists.

File: BIN · Numeric Edges
Use case: Scientific dataError handling+1· Paired fixture

Raw float64 Block: Little-Endian, No Header (.bin)

Sixteen doubles as a bare 128-byte block with no header, so byte order is knowledge the reader has to bring rather than something the file declares. It is one half of an endian pair that only a correct assumption tells apart.

File: BIN · Numeric Edges
Use case: Scientific dataError handling+1· Paired fixture

Raw float64 Endian Pair: Byte-Level Reference (.csv)

Every value in the raw endian pair with its exact byte sequence in both orders, so a decoder can be checked offset by offset instead of value by value. Negative zero and the subnormal entries are the rows where a byte-order mistake stops looking like a mistake.

File: CSV · Numeric Edges · 16 rows
Use case: Scientific dataEditor testing+1· Conversion set

Readonly and Disabled State Matrix (HTML)

Editable, read-only and disabled variants of the same controls side by side. Read-only values are submitted and disabled values are not, which is the distinction form scrapers and autofill tools most often get wrong.

File: HTML · Software Quality · 10 fields
Use case: Form testingForm parsing+3

Real-estate Listings (CSV, 30 rows)

A property-listings dataset: 30 homes with address, type, price, beds/baths, size, year built, coordinates, and status. Synthetic data for testing listing importers, map plots, and price analytics.

File: CSV · Real Estate · 30 rows
Use case: Data importGeospatial+1· Conversion set

Real-estate Listings (JSON, 30 records)

The property listings as a JSON array: the format twin of the CSV, for import and mapping tests.

File: JSON · Real Estate · 30 records
Use case: Data importGeospatial+1· Conversion set

Recommender Ratings: user/item/rating (CSV, 240 rows)

A MovieLens-style ratings log: 240 user/item/rating events with Unix timestamps across 50 users and 40 items. A fixture for testing recommender pipelines, collaborative-filtering loaders, and sparse-matrix builders.

File: CSV · Recommender · 240 rows
Use case: Data importModel evaluation+1

Recurring Donation (HTML)

Monthly recurring donation SAMPLE for nonprofit CRM tests.

File: HTML · Nonprofit · 3 fields
Use case: Form testingForm parsing+1

Redaction: SAMPLE PII Black-box Redacted (JPEG)

JPEG twin with SAMPLE PII fields blacked out. Pair with the clear JPEG to score redaction tools.

File: JPG · Redaction
Use case: OCR testing· Paired fixture

Redaction: SAMPLE PII Black-box Redacted (PDF)

The same SAMPLE PII document with email, phone, SSN, and address black-boxed. Pair with the unredacted twin to verify redaction completeness.

File: PDF · Redaction
Use case: PDF editor testing· Paired fixture

Redaction: SAMPLE PII Unredacted (JPEG)

JPEG twin of the unredacted SAMPLE PII page, for image-based redaction and OCR pipelines.

File: JPG · Redaction
Use case: OCR testingPDF editor testing· Paired fixture

Redaction: SAMPLE PII Unredacted (PDF)

A PDF with clearly labelled fictional SAMPLE PII fields: the unredacted twin for testing redaction tooling.

File: PDF · Redaction
Use case: PDF editor testingOCR testing· Paired fixture

Reference Letter Template (DOCX)

A professional reference letter recommending a former colleague, in standard block format: adapt the specifics and keep the structure.

File: DOCX · Reference Letter
Use case: Templates

Registration Form (HTML)

A downloadable sectioned registration form (personal details, account credentials, and address) with grouped fieldsets and native validation.

File: HTML · Account Registration · 9 fields
Use case: Form testingAutofill testing+2

Reject File - Hunks git apply Could Not Place

What `git apply --reject` leaves behind when a hunk will not apply: the failed hunks alone, under a header that is neither `diff --git` nor a plain `---`/`+++` pair. Ships with its .orig twin so the pair can drive a resolve-the-reject workflow end to end.

File: DIFF · Merges · UTF-8
Use case: Error handlingVisual diff / regression+1· Paired fixture

Rekor Transparency-Log Entry

A transparency-log entry keyed by its own UUID at the top level (a shape that breaks parsers expecting a fixed root key) with a base64 body that decodes to a dsse record. 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

Release SHA256SUMS Manifest

The oldest supply-chain artifact there is: a sha256sum manifest with the exact two-space separator the tool emits, listing a fictional release tarball and its nine dependency archives. Every package, version, hash and licence is fictional: the tree describes nothing real.

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

Repeated Array Field Names (HTML)

Controls that share a name on purpose: three tags[] text inputs, a multiple select and a checkbox group all submit repeated keys. This is valid form data, unlike the intentionally corrupt duplicate-name fixture shipped alongside it.

File: HTML · Software Quality · 6 fields
Use case: Form testingForm parsing+3· Conversion set