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 13 of 18; 24 results per page.

Show the canonical directory

Parquet — List Column

Parquet with a list-of-string column — tests repeated-field decoding.

File: PARQUET · Columnar
Use case: Data importConversion testing

Parquet — Mixed Nullable Types

Parquet with bool/int/string/float columns including a null integer.

File: PARQUET · Columnar
Use case: Data importConversion testing

Parquet — Nested Struct Column

Parquet with a struct column — tests nested type round-trips.

File: PARQUET · Columnar
Use case: Data importConversion testing

Parquet — Null-heavy Columns

Tiny Parquet table with null name/score/note cells — tests null handling in columnar readers.

File: PARQUET · Columnar · 3 rows
Use case: Data importConversion testing· Conversion set

Parquet — Single Row

Single-row Parquet table — minimal columnar fixture.

File: PARQUET · Columnar · 1 row
Use case: Data importConversion testing

Payment Instance — Invalid

Invalid payment JSON (negative amount, short currency) for schema error reporting tests.

File: JSON · Schema
Use case: Schema / OpenAPI testingError handling· Paired fixture

Payment Instance — Valid

Valid payment JSON instance paired with the payment JSON Schema.

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

Payment JSON Schema (draft-07)

Draft-07 JSON Schema for payment amount/currency validation in fintech API tests.

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

Payment Test Cards (CSV)

A reference list of well-known payment TEST card numbers (Visa, Mastercard, Amex, Discover, JCB, Diners) with sample CVV and expiry. These are published test values that pass the Luhn check but are not real accounts — for testing payment forms and card validators. Never use real card data.

File: CSV · Banking · 8 rows
Use case: Form testingData import

Payroll Summary (JSON)

A monthly payroll summary derived from the employee directory — headcount, annual and monthly gross totals, and a per-department breakdown. A fixture for testing finance/HR dashboards and JSON aggregation.

File: JSON · Hr
Use case: Data importConversion testing

PDB Structure — Water (.pdb)

The same water molecule in PDB format with fixed-column HETATM coordinate records and a CONECT bond record — for testing molecular-structure parsers and viewers and PDB/MOL conversion.

File: PDB · Scientific
Use case: Scientific dataEditor testing· Conversion set

Petstore OpenAPI 3.1 (Valid JSON)

A valid OpenAPI 3.1 pet-store SAMPLE spec in JSON — list/create pets with paginated responses for schema-validator and codegen tests.

File: JSON · Schema
Use case: Schema / OpenAPI testingJSON parsing+1· Conversion set

Petstore OpenAPI 3.1 (Valid YAML)

YAML twin of the valid pet-store OpenAPI spec — for testing YAML spec parsers and JSON↔YAML conversion.

File: YAML · Schema
Use case: Schema / OpenAPI testingJSON parsing+1· Conversion set

PKCS#12 Bundle (.p12)

A PKCS#12 (.p12/PFX) bundle packaging the sample RSA key and certificate together, protected with the sample password 'novus-sample' — for testing keystore importers and PKCS#12 parsers. (The PKCS#12 MAC salt is random, so this file is intentionally not byte-stable.)

File: P12 · Security
Use case: Certificate & key testing

PlantUML Sequence Diagram

A PlantUML sequence diagram of an order interaction (customer, store, warehouse) as diagrams-as-code — for testing PlantUML parsing and diagram rendering pipelines.

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

POS SKU Catalog (CSV)

A point-of-sale SKU catalog with tax codes and active flags — fictional Meridian Supply inventory. CSV twin.

File: CSV · Pos · 8 rows
Use case: Data importCSV parsing· Conversion set

POS SKU Catalog (JSON)

A point-of-sale SKU catalog with tax codes and active flags — fictional Meridian Supply inventory. JSON twin.

File: JSON · Pos · 8 records
Use case: Data importJSON parsing· Conversion set

Postgres SQL Dump

A Postgres-flavour SQL dump with a CREATE TABLE and INSERT statements — for testing SQL importers and migrations.

File: SQL · Sql · 2 rows
Use case: SQL import

Product Instance — Invalid (JSON)

A product object that deliberately violates the product JSON Schema in five ways (out-of-range id, empty name, non-positive price, wrong boolean type, an extra property) — the negative case for testing validator error reporting.

File: JSON · Schema
Use case: Schema validationError handling· Paired fixture

Product Instance — Valid (JSON)

A product object that conforms to the product JSON Schema — the positive case for testing a JSON-Schema validator.

File: JSON · Schema
Use case: Schema validation· Paired fixture

Product JSON Schema (draft-07)

A JSON Schema (draft-07) describing a product object, with required fields, types, and constraints — paired with a conforming and a deliberately non-conforming instance for testing validators.

File: JSON · Schema
Use case: Schema validationData import· Conversion set

Protobuf — Encoded Message

A single protobuf User message in binary wire format (varint + length-delimited fields) — the serialized counterpart to the user.proto schema. For testing protobuf decoders without the generated code.

File: PB · Binary · 5 rows
Use case: Conversion testingSerialization testing

Protocol Buffers Schema (proto3)

A proto3 Protocol Buffers schema with messages, an enum, and a repeated field — for testing protobuf compilers (protoc), codegen, and schema tooling.

File: PROTO · Api
Use case: API testingConversion testing

Protocol Buffers Schema Evolution - Backward-Compatible

The compatible proto3 Customer message for field-number and wire-compatibility testing. Backward compatible: existing field numbers/types are retained and optional email uses new field number 3.

File: PROTO · Schema · 4 fields
Use case: Schema / OpenAPI testingSchema validation+2· Conversion set