Explore the test library

Search files, editable visual templates, and live browser targets from one registry-backed directory. Filtered query views stay crawlable for links but are deliberately noindex; the stable taxonomy pages below remain the canonical search surfaces.

Filter the library

SearchTypeCategorySubcategoryFormatUse caseLive targetSort

430 results

Page 10 of 18; 24 results per page.

Show the canonical directory

JSON Schema (User)

A draft-07 JSON Schema describing a user object — for testing schema validators and schema-aware tooling.

File: JSON · JSON · UTF-8
Use case: Schema validationJSON parsing

JSON Schema allOf Merge

JSON Schema allOf merging id and name requirements — tests composite schema validation.

File: JSON · Schema
Use case: Schema / OpenAPI testing

JSON Schema Edge — Additional Properties False

Minimal JSON Schema SAMPLE focusing on additional properties false constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Array Unique Items

Minimal JSON Schema SAMPLE focusing on array unique items constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Dependent Required

Minimal JSON Schema SAMPLE focusing on dependent required constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Enum Currency

Minimal JSON Schema SAMPLE focusing on enum currency constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Format Uri Email

Minimal JSON Schema SAMPLE focusing on format uri email constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Nullable Optional

Minimal JSON Schema SAMPLE focusing on nullable optional constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — One Of Status

Minimal JSON Schema SAMPLE focusing on one of status constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema Edge — Pattern Sku

Minimal JSON Schema SAMPLE focusing on pattern sku constraints.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+1· Conversion set

JSON Schema oneOf Union

JSON Schema with a oneOf union over string vs number tagged objects — for testing union validation.

File: JSON · Schema
Use case: Schema / OpenAPI testing

JSON Schema Schema Evolution - Backward-Compatible

The compatible member of a JSON Schema 2020-12 customer contract. Backward compatible: existing instances remain valid because email is optional.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

JSON Schema Schema Evolution - Baseline

The baseline member of a JSON Schema 2020-12 customer contract. Reference contract: id and name are required strings.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

JSON Schema Schema Evolution - Breaking

The breaking member of a JSON Schema 2020-12 customer contract. Breaking relative to baseline: id changes from string to integer and tenantId becomes required.

File: JSON · Schema
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set

JSON with Duplicate Keys

A JSON object that repeats several member names (name, tags, timeout, active). RFC 8259 permits duplicate keys but leaves the result parser-defined — most keep the last. A fixture for testing how a JSON parser resolves duplicates.

File: JSON · Edge Cases
Use case: JSON parsingError handling

JSON-Lines Application Log

A structured application log with one JSON object per line at info/debug/warn/error levels — for testing log ingestion.

File: JSONL · Logs · 4 records
Use case: Log parsing

Jupyter Notebook (IPYNB)

A valid Jupyter notebook (nbformat 4.5) with markdown cells, code cells, and real outputs (stdout stream and an execute result) — for testing notebook parsers, nbconvert, and JSON tooling.

File: IPYNB · Notebooks
Use case: JSON parsingConversion testing+1

KML Places

A KML document with named placemarks — for testing Google Earth / mapping importers.

File: KML · Geospatial · UTF-8
Use case: Geospatial

Kubernetes Component Log — klog (log)

A Kubernetes-component log in the klog/glog format — a severity letter, timestamp, thread id, and source location prefix followed by the message. A fixture for testing klog parsers and severity extraction.

File: LOG · Logs
Use case: Log parsingObservability

Kubernetes SAMPLE — Configmap (YAML)

SAMPLE Kubernetes configmap manifest — fictional names, no real cluster secrets.

File: YAML · Config
Use case: Config testingConversion testing

Kubernetes SAMPLE — Deployment (YAML)

SAMPLE Kubernetes deployment manifest — fictional names, no real cluster secrets.

File: YAML · Config
Use case: Config testingConversion testing

Kubernetes SAMPLE — Ingress (YAML)

SAMPLE Kubernetes ingress manifest — fictional names, no real cluster secrets.

File: YAML · Config
Use case: Config testingConversion testing

Kubernetes SAMPLE — Secret (YAML)

SAMPLE Kubernetes secret manifest — fictional names, no real cluster secrets.

File: YAML · Config
Use case: Config testingConversion testing

Kubernetes SAMPLE — Service (YAML)

SAMPLE Kubernetes service manifest — fictional names, no real cluster secrets.

File: YAML · Config
Use case: Config testingConversion testing