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 60 of 221; 24 results per page.

Show the canonical directory

Docker Compose File (YAML)

A sample docker-compose file defining a web service with Postgres and Redis dependencies, for testing Compose parsers and YAML tooling.

File: YML · Config
Use case: Config testingConversion testing

Docker Compose File, Intentionally Invalid

An intentionally invalid Compose file: services as a list, a service with both image and an empty build, an unquoted 8080:8080 port that YAML 1.1 reads as a base-60 integer, and a depends_on naming an undefined service.

File: YAML · Docker
Use case: Error handlingConfig parsing+1

Docker Compose Override (YAML)

Sample docker-compose override file for merge/extends parser tests.

File: YML · Config
Use case: Config testingConversion testing

Docker Compose Profiles

Five Compose services across three profiles, one of which belongs to two profiles at once. Services with no profiles key always start; the rest are opt-in, which is the selection logic this fixture exists to test.

File: YAML · Docker
Use case: Config testingConfig parsing+1

Docker Compose Specification (No version Key)

A Compose Specification file with no top-level version key, condition-based depends_on, healthchecks, and a deploy resource limit. Parsers written against the older schema often require the version key, which is exactly what this fixture separates.

File: YAML · Docker
Use case: Config testingConfig parsing+1

Docker Container Log: json-file driver (log)

A Docker json-file container log: one JSON object per line with the log text, stream (stdout/stderr), and an RFC 3339 timestamp, exactly as Docker's default logging driver writes it. A fixture for container-log shippers and parsers.

File: LOG · Logs
Use case: Log parsingObservability+1

Dockerfile (multi-stage)

A sample multi-stage Dockerfile with a build stage and a slim runtime stage, for testing Dockerfile parsers, linters (hadolint), and syntax highlighting. Illustrative only.

File: DOCKERFILE · Config
Use case: Config testingConversion testing

Dockerfile, Multi-Stage Build Definition

A three-stage Dockerfile with a syntax directive, build args interpolated into FROM lines, a heredoc COPY, multi-line LABEL and ENV continuations, a non-root USER, and HEALTHCHECK in exec form. Inert: every base image is a fictional example.invalid reference.

File: DOCKERFILE · Docker
Use case: Config parsingSyntax highlighting+1

DOCX with Comments

A Word document with two anchored reviewer comments, for testing comment extraction and whether converters preserve or drop review annotations.

File: DOCX · Word
Use case: Conversion testing

DOCX with Core and Custom Properties

A valid DOCX package with fixed core properties and two custom properties surrounding an unchanged word/document.xml part.

File: DOCX · Word
Use case: Metadata testingConversion testing· Paired fixture

DOCX with Metadata Stripped

The same DOCX document part without core or custom property parts, suitable for checking OOXML metadata removal without content loss.

File: DOCX · Word
Use case: Metadata testingConversion testing· Paired fixture

DOCX with Tracked Changes

A Word document with real tracked changes (insertions and deletions attributed to two reviewers with timestamps) for testing how tools read, accept, reject, or preserve revisions.

File: DOCX · Word
Use case: Conversion testing

Donation Pledge AcroForm (SAMPLE)

Nonprofit donation/pledge form for fundraising CRM import tests.

File: PDF · Nonprofit · 3 fields
Use case: Form testingPDF form filling+2

Donation Pledge Field Manifest (JSON)

Field manifest JSON for the Wave F nonprofit form: names, types, and SAMPLE defaults.

File: JSON · Nonprofit · 1 field
Use case: Form parsingForm testing

Donation Pledge Form (HTML)

Nonprofit donation/pledge form for fundraising CRM import tests.

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

Donation Pledge Sample Export (CSV)

SAMPLE CSV export row for the nonprofit form submission shape.

File: CSV · Nonprofit
Use case: Form testingCSV parsing

Donation Pledge Sample Response (JSON)

SAMPLE submitted-field snapshot JSON for the donation pledge form.

File: JSON · Nonprofit
Use case: Form testingJSON parsing+1

Donation Tax Receipt (SAMPLE PDF)

Nonprofit tax receipt SAMPLE for donation acknowledgment tests.

File: PDF · Nonprofit · 3 fields
Use case: Form testingPDF form filling+2

DPA Annex: Subprocessors (CSV, SAMPLE)

CSV Annex A twin listing fictional SAMPLE subprocessors for the deep DPA.

File: CSV · DPA Annex · 3 rows
Use case: TemplatesPrivacy export testing+1· Conversion set

DPA Deep (DOCX, SAMPLE)

Deeper SAMPLE data processing addendum DOCX with annex summary, not legal advice.

File: DOCX · DPA
Use case: TemplatesPrivacy export testing· Conversion set

DPA Deep (PDF, SAMPLE)

PDF twin of the deep SAMPLE DPA.

File: PDF · DPA
Use case: TemplatesPDF editor testing+1· Conversion set

draw.io Diagram (XML)

A draw.io (diagrams.net) diagram in its native mxGraphModel XML (a small flowchart) for testing draw.io import/export and XML parsing of diagram files.

File: DRAWIO · Diagrams
Use case: Conversion testingEditor testing· Conversion set

DSSE Envelope With Undecodable Payload: Intentionally Corrupt

An intentionally corrupt DSSE envelope: the JSON parses and the signature block looks complete, but the payload is truncated and contains characters outside the base64 alphabet. 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: Error handlingJSON parsing· Conversion set

DSSE Envelope Wrapping a Provenance Statement

A DSSE envelope whose base64 payload decodes to the SLSA v1 statement in this family: the wrapper attestation tooling actually transports. 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 parsingJWT / JWKS testing+1· Conversion set