What CSV edge cases do you cover?

Encoding matrix (UTF-8 BOM, UTF-16, CP1252, Shift-JIS, Latin-1), delimiter variants, fixed-width, ragged rows, quoted newlines, and domain mini-datasets (SaaS, POS, lab, marketing).

Are datasets realistic or random?

Schemas are documented and values are deterministic synthetic SAMPLE data — shaped like production exports without real customer PII.

How do I test encoding detection?

Filter Browse by purpose encoding-detection or open the encodings subcategory under Data.

Do you include OpenAPI, JSON Schema, or time-series edges?

Yes — later waves add valid/invalid schema twins, pagination and webhook API fixtures, and irregular timestamp / DST-gap series. Filter by schema-testing or timeseries-testing.

Data — example & test files

Api

Api Batch Response

Batch API response mixing success and failure per sub-request.

File: JSON · Api
Use case: API testingJSON parsing

API Cursor Pagination — Page 1 (JSON)

Cursor-paginated SAMPLE API response page 1 with nextCursor metadata.

File: JSON · Api
Use case: API testingJSON parsing· Conversion set

API Cursor Pagination — Page 2 (JSON)

Cursor-paginated SAMPLE API response page 2 with nextCursor metadata.

File: JSON · Api
Use case: API testingJSON parsing· Conversion set

Api Empty Page Response

Empty paginated response — edge case for UI empty states and merge logic.

File: JSON · Api
Use case: API testingJSON parsing

API Error — 404 (RFC 9457 problem+json)

A 404 error body in RFC 9457 (problem+json) form, with type, title, status, detail, and instance — for testing structured error handling and problem-detail parsers.

File: JSON · Api
Use case: API testingConversion testing

API Error — 422 Validation (JSON)

A 422 validation-error response with a machine-readable list of field errors — for testing form-validation surfacing and error mapping.

File: JSON · Api
Use case: API testingConversion testing

Api Link Header Pagination

RFC 5988 Link header pagination metadata as JSON for HTTP client tests.

File: JSON · Api
Use case: API testingJSON parsing

Api Nested Comments Pagination

Nested pagination object for comments under a post — tests deeply nested page tokens.

File: JSON · Api
Use case: API testingJSON parsing

API Offset Pagination — Page 1 (JSON)

Offset/limit paginated SAMPLE response page 1 for list-merge tests.

File: JSON · Api
Use case: API testingJSON parsing· Conversion set

API Offset Pagination — Page 2 (JSON)

Offset/limit paginated SAMPLE response page 2 for list-merge tests.

File: JSON · Api
Use case: API testingJSON parsing· Conversion set

API Problem+JSON — Bad Request (400)

RFC 7807 SAMPLE problem document for HTTP 400 (Bad Request) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Conflict (409)

RFC 7807 SAMPLE problem document for HTTP 409 (Conflict) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Forbidden (403)

RFC 7807 SAMPLE problem document for HTTP 403 (Forbidden) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Gone (410)

RFC 7807 SAMPLE problem document for HTTP 410 (Gone) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Internal Server Error (500)

RFC 7807 SAMPLE problem document for HTTP 500 (Internal Server Error) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Not Acceptable (406)

RFC 7807 SAMPLE problem document for HTTP 406 (Not Acceptable) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Not Found (404)

RFC 7807 SAMPLE problem document for HTTP 404 (Not Found) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Service Unavailable (503)

RFC 7807 SAMPLE problem document for HTTP 503 (Service Unavailable) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Too Many Requests (429)

RFC 7807 SAMPLE problem document for HTTP 429 (Too Many Requests) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Unauthorized (401)

RFC 7807 SAMPLE problem document for HTTP 401 (Unauthorized) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Unprocessable Entity (422)

RFC 7807 SAMPLE problem document for HTTP 422 (Unprocessable Entity) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

API Problem+JSON — Unsupported Media Type (415)

RFC 7807 SAMPLE problem document for HTTP 415 (Unsupported Media Type) client tests.

File: JSON · Api
Use case: JSON parsingError handling+1· Conversion set

Api Rate Limit Meta

Rate-limit header values captured as JSON for middleware testing.

File: JSON · Api
Use case: API testingJSON parsing

API Response — Users Page 1 (JSON)

Page 1 of a paginated JSON API response (users), with page metadata and a `hasMore` flag. Paired with page 2 for testing pagination and infinite-scroll logic.

File: JSON · Api
Use case: API testingConversion testing· Conversion set

API Response — Users Page 2 (JSON)

Page 2 (the final page) of a paginated JSON API response. Paired with page 1 for testing pagination, `hasMore` handling, and list merging.

File: JSON · Api
Use case: API testingConversion testing· Conversion set

Api Total Count Mismatch

Paginated response where total count disagrees with items length — tests inconsistency detection.

File: JSON · Api
Use case: API testingJSON parsing

GraphQL Error Response (JSON)

GraphQL error response with message and location — negative case for GraphQL clients.

File: JSON · Api
Use case: API testingJSON parsing+1

Graphql Introspection Fragment

Partial GraphQL introspection result for schema-stitching tests.

File: JSON · Api
Use case: API testingJSON parsing

GraphQL Mutation Response (JSON)

Sample GraphQL mutation success payload for testing mutation handlers.

File: JSON · Api
Use case: API testingJSON parsing

GraphQL Query Response (JSON)

Sample GraphQL query response with nested user and orders — for GraphQL client tests.

File: JSON · Api
Use case: API testingJSON parsing

GraphQL Schema (SDL)

A GraphQL Schema Definition Language (SDL) file with queries, a mutation, object/input types, and an enum — for testing GraphQL schema parsers, linters, and code generators.

File: GRAPHQL · Api
Use case: API testingConversion testing

Graphql Subscription Event

GraphQL subscription event payload for realtime client tests.

File: JSON · Api
Use case: API testingJSON parsing

OpenAPI 3.1 Spec (JSON)

A small but complete OpenAPI 3.1 description (two paths, three schemas) in JSON — for testing API tooling, mock servers, client codegen, and docs generators.

File: JSON · Api
Use case: API testingConversion testing· Conversion set

OpenAPI 3.1 Spec (YAML)

The same OpenAPI 3.1 description in YAML — the format most API definitions ship in. Paired with the JSON twin for testing YAML↔JSON conversion and spec parsers.

File: YAML · Api
Use case: API testingConversion testing· Conversion set

Openapi Callback Payload

Callback payload matching the Wave F webhook OpenAPI SAMPLE.

File: JSON · Api
Use case: API testingJSON parsing

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

Webhook Hmac Signature Sample

Documented HMAC webhook signature SAMPLE — no real secret, for verifier unit tests.

File: JSON · Api
Use case: API testingJSON parsing

Webhook Payload — Github Push (JSON)

SAMPLE github push webhook JSON body for signature-verification and parser tests.

File: JSON · Api
Use case: API testingJSON parsing

Webhook Payload — Slack Message (JSON)

SAMPLE slack message webhook JSON body for signature-verification and parser tests.

File: JSON · Api
Use case: API testingJSON parsing

Webhook Payload — Stripe Payment (JSON)

SAMPLE stripe payment webhook JSON body for signature-verification and parser tests.

File: JSON · Api
Use case: API testingJSON parsing

Banking

Bank Transactions (CSV, 60 rows)

A bank-transaction statement — 60 debits and credits across three accounts (masked numbers) with running balances, categories, and merchants. Synthetic data for testing statement parsers, categorisation, and reconciliation.

File: CSV · Banking · 60 rows
Use case: Data importConversion testing· Conversion set

Bank Transactions (JSON, 60 records)

The bank transactions as a JSON array — the format twin of the CSV, for import and reconciliation testing.

File: JSON · Banking · 60 records
Use case: Data importConversion testing· Conversion set

ISO 20022 Credit Transfer — pain.001 (XML)

A sample ISO 20022 customer credit-transfer initiation (pain.001.001.09) — a single payment with debtor/creditor parties, IBANs, BICs, amount, and remittance info. IBANs are published documentation examples; a fixture for testing payment-message parsers and bank integrations.

File: XML · Banking
Use case: Data importConversion testing+1

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

Binary

Avro — Row Binary + Schema

The same records as Apache Avro — a compact row-based binary format that embeds its own schema, widely used in Kafka pipelines. For testing Avro decoders and schema evolution.

File: AVRO · Binary · 5 rows
Use case: Conversion testingData engineering· Conversion set

BSON — Binary JSON (MongoDB)

The records as BSON — the binary-JSON encoding MongoDB stores documents in. For testing BSON decoders and JSON↔BSON conversion.

File: BSON · Binary · 5 rows
Use case: Conversion testingSerialization testing· Conversion set

CBOR — Concise Binary Object

The records as CBOR — the IETF concise binary object representation used in IoT and COSE/WebAuthn. For testing CBOR decoders and JSON↔CBOR conversion.

File: CBOR · Binary · 5 rows
Use case: Conversion testingSerialization testing· Conversion set

DBF — dBase / xBase Table

The employee table as a dBase (DBF) file — the venerable xBase table format still emitted by GIS tools and legacy databases. For testing DBF readers and DBF→CSV conversion.

File: DBF · Binary · 5 rows
Use case: Conversion testing

Feather — Arrow IPC Table

The same table as Feather (Arrow IPC file) — the zero-copy on-disk form of an Apache Arrow table. For testing Arrow readers and fast columnar interchange.

File: FEATHER · Binary · 5 rows
Use case: Conversion testingData engineering· Conversion set

HDF5 — Hierarchical Scientific Data

A small HDF5 file with a compound 'employees' dataset and a numeric 'readings' grid — the hierarchical format used across science and ML. For testing h5py/HDF5 readers and conversion.

File: H5 · Binary · 5 rows
Use case: Conversion testingData engineering

MessagePack — Binary JSON

The records as MessagePack — a compact binary serialization that maps onto the JSON data model, common in caches and RPC. For testing MessagePack codecs and JSON↔MessagePack conversion.

File: MSGPACK · Binary · 5 rows
Use case: Conversion testingSerialization testing· Conversion set

ORC — Columnar Table

The same employee table as Apache ORC — the columnar format common in the Hive/Hadoop ecosystem. For testing ORC readers and Parquet↔ORC conversion.

File: ORC · Binary · 5 rows
Use case: Conversion testingData engineering· Conversion set

Parquet — Columnar Table

A small employee table as Apache Parquet — the columnar format at the heart of modern data lakes and analytics. For testing Parquet readers (pandas, Spark, DuckDB) and conversion.

File: PARQUET · Binary · 5 rows
Use case: Conversion testingData engineering· 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

Calendar Contacts

Calendar Parsing - Intentionally Corrupt Missing END:VEVENT (ICS)

An intentionally corrupt iCalendar file whose VEVENT is never closed, for testing fatal component-nesting errors without using a large or hostile payload.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Parsing - Recoverable LF Line Endings (ICS)

A complete iCalendar structure using LF-only line endings, a common recoverable export defect for tolerant parser tests.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Parsing - Valid Folded UTF-8 Event (ICS)

A standards-conforming event with a folded content line and UTF-8 text for baseline parser and line-unfolding tests.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Recurrence - EXDATE plus RDATE (ICS)

A recurrence set with both an exclusion and an explicit addition, useful for catching expansion engines that apply only one modifier.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Recurrence - Five Weekly Occurrences (ICS)

A weekly five-occurrence series that provides the recurrence baseline before exclusions or additions are applied.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Recurrence - Weekly Series with EXDATE (ICS)

The same weekly series with its third occurrence excluded, for testing RRULE expansion followed by EXDATE filtering.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Scheduling Lifecycle - CANCEL (ICS)

The terminal cancellation for the scheduling group, checking METHOD, STATUS, UID and sequence precedence together.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Scheduling Lifecycle - REPLY (ICS)

An attendee acceptance for the same meeting, used to test UID correlation and PARTSTAT state updates.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Scheduling Lifecycle - REQUEST (ICS)

The invitation that starts a scheduling lifecycle, using stable UID and organizer/attendee identities.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Time Zone - Equivalent UTC Event (ICS)

The UTC representation of the Toronto event, providing an exact normalization target for calendar importers.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Time Zone - Floating Local Time (ICS)

A floating-time variant with no TZID or Z suffix, for verifying that parsers do not silently reinterpret local wall time as UTC.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Calendar Time Zone - Toronto after DST Transition (ICS)

A TZID-qualified event immediately after Toronto's spring-forward boundary, with an explicit VTIMEZONE definition.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsingConversion testing· Conversion set

Embedded-Photo Contact - vCard 2.1

A fictional contact carrying the same tiny portrait in the version-specific photo syntax used by vCard 2.1, 3.0 and 4.0. This member uses vCard 2.1 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

Embedded-Photo Contact - vCard 3.0

A fictional contact carrying the same tiny portrait in the version-specific photo syntax used by vCard 2.1, 3.0 and 4.0. This member uses vCard 3.0 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

Embedded-Photo Contact - vCard 4.0

A fictional contact carrying the same tiny portrait in the version-specific photo syntax used by vCard 2.1, 3.0 and 4.0. This member uses vCard 4.0 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

iCalendar Event

An iCalendar (.ics) file with a single event and CRLF line endings per spec — for testing calendar imports.

File: ICS · Calendar Contacts · UTF-8
Use case: Calendar parsing

Multi-Value Contact - vCard 2.1

A fictional contact with repeated typed properties for testing importers that otherwise keep only the first value. This member uses vCard 2.1 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

Multi-Value Contact - vCard 3.0

A fictional contact with repeated typed properties for testing importers that otherwise keep only the first value. This member uses vCard 3.0 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

Multi-Value Contact - vCard 4.0

A fictional contact with repeated typed properties for testing importers that otherwise keep only the first value. This member uses vCard 4.0 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

Organization and Address Contact - vCard 2.1

A fictional business contact with structured organization and postal-address fields for CRM migration tests. This member uses vCard 2.1 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

Organization and Address Contact - vCard 3.0

A fictional business contact with structured organization and postal-address fields for CRM migration tests. This member uses vCard 3.0 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

Organization and Address Contact - vCard 4.0

A fictional business contact with structured organization and postal-address fields for CRM migration tests. This member uses vCard 4.0 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

Unicode Contact - vCard 2.1

A fictional multilingual contact for checking Unicode decoding and round trips between legacy and current vCard versions. This member uses vCard 2.1 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

Unicode Contact - vCard 3.0

A fictional multilingual contact for checking Unicode decoding and round trips between legacy and current vCard versions. This member uses vCard 3.0 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

Unicode Contact - vCard 4.0

A fictional multilingual contact for checking Unicode decoding and round trips between legacy and current vCard versions. This member uses vCard 4.0 syntax.

File: VCF · Calendar Contacts
Use case: Contact parsingConversion testing· Conversion set

vCard Contact

A vCard 3.0 contact with name, email, phone, and address — for testing contact importers.

File: VCF · Calendar Contacts · UTF-8
Use case: Contact parsing

Columnar

Columnar Nulls Schema (JSON)

JSON description of nullable columns in the null-heavy columnar fixtures.

File: JSON · Columnar
Use case: Data importConversion testing+1· Conversion set

Feather — Dictionary-encoded Column

Feather file with dictionary-encoded strings — Arrow IPC edge-case fixture.

File: FEATHER · Columnar
Use case: Data importConversion testing

Feather — Null-heavy Columns

Feather/Arrow IPC twin of the null-heavy table — grouped with the Parquet nulls fixture.

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

Parquet — Decimal as String Column

Amounts stored as strings in Parquet — common ingestion edge case for ETL parsers.

File: PARQUET · Columnar · 2 rows
Use case: Data importConversion testing

Parquet — Dictionary-encoded Column

Parquet with dictionary-encoded string column — tests dictionary page decoding.

File: PARQUET · Columnar · 5 rows
Use case: Data importConversion testing

Parquet — Duplicate Key Column

Parquet with repeated key values — tests join/aggregation edge cases.

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

Parquet — Empty Table

Empty Parquet file with schema but no rows — edge case for readers.

File: PARQUET · Columnar · 0 rows
Use case: Data importConversion testing

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

Config

Apache .htaccess Sample

Tiny Apache rewrite rules SAMPLE for .htaccess parser tests.

File: TXT · Config
Use case: Config testingConversion testing

App Config (INI)

Sample INI config file for legacy config parser tests.

File: INI · Config
Use case: Config testingConversion testing

App Config (TOML)

Sample TOML application config for TOML parser tests.

File: TOML · Config
Use case: Config testingConversion testing

App Settings (JSON)

JSON application settings for config-merge and validation tests.

File: JSON · Config
Use case: Config testingConversion testing+1

AWS Credentials Shape SAMPLE (INI)

AWS credentials file shape with obviously fake keys — for credential scanner and parser tests.

File: INI · Config
Use case: Config testingConversion testing

CI Pipeline Config (YAML)

Minimal CI pipeline YAML for GitHub Actions / GitLab CI parser tests.

File: YML · Config
Use case: Config testingConversion testing

Config — App Feature Flags (JSON)

Tiny SAMPLE JSON config fixture (app-feature-flags) for parser and twin tests.

File: JSON · Config
Use case: Config parsingEditor testing· Conversion set

Config — App Feature Flags (TOML)

Tiny SAMPLE TOML config fixture (app-feature-flags) for parser and twin tests.

File: TOML · Config
Use case: Config parsingEditor testing· Conversion set

Config — App Feature Flags (YAML)

Tiny SAMPLE YAML config fixture (app-feature-flags) for parser and twin tests.

File: YAML · Config
Use case: Config parsingEditor testing· Conversion set

Config — Cors Origins (JSON)

Tiny SAMPLE JSON config fixture (cors-origins) for parser and twin tests.

File: JSON · Config
Use case: Config parsingEditor testing· Conversion set

Config — Database Pool (ENV)

Tiny SAMPLE ENV config fixture (database-pool) for parser and twin tests.

File: ENV · Config
Use case: Config parsingEditor testing· Conversion set

Config — Database Pool (INI)

Tiny SAMPLE INI config fixture (database-pool) for parser and twin tests.

File: INI · Config
Use case: Config parsingEditor testing· Conversion set

Config — K8S Resource Snippet (YAML)

Tiny SAMPLE YAML config fixture (k8s-resource-snippet) for parser and twin tests.

File: YAML · Config
Use case: Config parsingEditor testing· Conversion set

Config — Logging Levels (INI)

Tiny SAMPLE INI config fixture (logging-levels) for parser and twin tests.

File: INI · Config
Use case: Config parsingEditor testing· Conversion set

Config — Rate Limit (YAML)

Tiny SAMPLE YAML config fixture (rate-limit) for parser and twin tests.

File: YAML · Config
Use case: Config parsingEditor testing· Conversion set

Config — Redis Cache (TOML)

Tiny SAMPLE TOML config fixture (redis-cache) for parser and twin tests.

File: TOML · Config
Use case: Config parsingEditor testing· Conversion set

Config — Redis Cache (YAML)

Tiny SAMPLE YAML config fixture (redis-cache) for parser and twin tests.

File: YAML · Config
Use case: Config parsingEditor testing· Conversion set

Config — Smtp Relay (ENV)

Tiny SAMPLE ENV config fixture (smtp-relay) for parser and twin tests.

File: ENV · Config
Use case: Config parsingEditor testing· Conversion set

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 Override (YAML)

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

File: YML · Config
Use case: Config testingConversion testing

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

Environment File — Comments Edge (.env)

SAMPLE .env file (comments-edge) for dotenv parser and config-loader tests — placeholders only.

File: ENV · Config
Use case: Config testingConversion testing

Environment File — Development (.env)

SAMPLE .env file (development) for dotenv parser and config-loader tests — placeholders only.

File: ENV · Config
Use case: Config testingConversion testing

Environment File — Production Template (.env)

SAMPLE .env file (production-template) for dotenv parser and config-loader tests — placeholders only.

File: ENV · Config
Use case: Config testingConversion testing

Environment File — Testing (.env)

SAMPLE .env file (testing) for dotenv parser and config-loader tests — placeholders only.

File: ENV · Config
Use case: Config testingConversion testing

Environment File (.env template)

A sample environment (.env) file with typical configuration keys and placeholder values — for testing dotenv parsers and config loaders. Contains no real secrets.

File: ENV · Config
Use case: Config testingConversion testing

INI Configuration

A classic INI configuration file with sections and key/value pairs — for testing INI parsers.

File: INI · Config · UTF-8
Use case: Config parsing

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

Nginx Sample Config

Minimal nginx reverse-proxy config SAMPLE for syntax highlighter and linter tests.

File: TXT · Config
Use case: Config testingConversion testing

Terraform tfvars SAMPLE

Sample terraform.tfvars with fictional region — for HCL/tfvars parser tests.

File: TXT · Config
Use case: Config testingConversion testing

TOML Configuration

A TOML configuration file with tables, inline values, and an array of tables — for testing TOML parsers.

File: TOML · Config · UTF-8
Use case: Config parsing

Web App Manifest (webmanifest)

A W3C Web App Manifest (JSON) with name, theme colours, and icon set — for testing PWA install prompts and manifest validators.

File: WEBMANIFEST · Config
Use case: Config testingConversion testing

CSV

10,000-Row CSV

A CSV with 10,000 data rows — for testing streaming parsers, memory handling, and import performance.

File: CSV · CSV · 10,000 rows
Use case: CSV parsingData import

Clean CSV

A clean, well-formed CSV with a header and 20 rows — the baseline case for CSV parser testing.

File: CSV · CSV · 20 rows
Use case: CSV parsingData import

CSV Edge — Empty Fields

Tiny SAMPLE CSV (empty-fields) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge — Hash Commented

Tiny SAMPLE CSV (hash-commented) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge — Header Only

Tiny SAMPLE CSV (header-only) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge — Mixed Quoting

Tiny SAMPLE CSV (mixed-quoting) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge — Pipe Delimited

Tiny SAMPLE CSV (pipe-delimited) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge — Quoted Embedded Comma

Tiny SAMPLE CSV (quoted-embedded-comma) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge — Quoted Embedded Newline

Tiny SAMPLE CSV (quoted-embedded-newline) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge — Semicolon Eu

Tiny SAMPLE CSV (semicolon-eu) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge — Single Column

Tiny SAMPLE CSV (single-column) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

CSV Edge — Trailing Comma

Tiny SAMPLE CSV (trailing-comma) exercising delimiter/quoting edge behaviour.

File: CSV · CSV
Use case: CSV parsingError handling+1· Conversion set

Headerless CSV

A CSV with no header row — for testing parsers that must infer or be told the column names.

File: CSV · CSV · 20 rows
Use case: CSV parsing

Latin-1 Encoded CSV

A CSV encoded in Latin-1 (ISO-8859-1) with accented names — for testing encoding detection and mis-decoding (it will look wrong if read as UTF-8).

File: CSV · CSV · 3 rows
Use case: CSV parsingEncoding detection

Messy CSV (quoted commas, newlines, ragged rows)

A deliberately messy CSV: a quoted field with a comma, a quoted field with an embedded newline, escaped double-quotes, and ragged rows with too few and too many fields — the cases that break naïve parsers.

File: CSV · CSV · UTF-8
Use case: CSV parsingError handling

Semicolon-Delimited CSV

A CSV that uses semicolons as the delimiter (common in European locales) — for testing delimiter detection.

File: CSV · CSV · 20 rows
Use case: CSV parsing

Tab-Separated Values (TSV)

A tab-separated values file with a header and 20 rows — for testing TSV parsing and delimiter handling.

File: TSV · CSV · 20 rows
Use case: CSV parsing

Database

Sample SQLite Database

A real SQLite database with two related tables — users and orders joined by a foreign key — for testing database importers and SQL tooling.

File: SQLITE · Database
Use case: Data import

Diagrams

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

Graphviz DOT Graph

A Graphviz DOT directed graph describing a fulfilment pipeline — for testing DOT parsing, Graphviz rendering, and DOT-to-SVG/PNG conversion.

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

Mermaid Flowchart (MMD)

A Mermaid flowchart of an order-fulfilment process as diagrams-as-code — for testing Mermaid rendering, diagram-to-image conversion, and Markdown pipelines that embed Mermaid.

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

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

Ecommerce

E-commerce Customers (CSV, 500 rows)

A realistic e-commerce customer directory (500 rows) — part of a relational dataset (products, customers, orders) with CSV, JSON, SQL, and Parquet twins for testing joins, imports, and conversion.

File: CSV · Ecommerce · 500 rows
Use case: Data importConversion testing+1· Conversion set

E-commerce Customers (JSON, 500 records)

The e-commerce customers table as a JSON array — the format twin of the CSV, for import and conversion testing.

File: JSON · Ecommerce · 500 records
Use case: Data importConversion testing· Conversion set

E-commerce Database Schema (SQL)

A relational SQL schema (products, customers, orders with primary and foreign keys) plus sample INSERTs — the DDL twin of the e-commerce dataset, for testing schema import and migrations.

File: SQL · Ecommerce
Use case: Data importConversion testing

E-commerce Orders (CSV, 2000 rows)

A realistic e-commerce order lines (customer_id → customers, product_id → products) (2000 rows) — part of a relational dataset (products, customers, orders) with CSV, JSON, SQL, and Parquet twins for testing joins, imports, and conversion.

File: CSV · Ecommerce · 2,000 rows
Use case: Data importConversion testing+1· Conversion set

E-commerce Orders (JSON, 2000 records)

The e-commerce orders table as a JSON array — the format twin of the CSV, for import and conversion testing.

File: JSON · Ecommerce · 2,000 records
Use case: Data importConversion testing· Conversion set

E-commerce Orders (Parquet, 2000 rows)

The e-commerce orders table as Apache Parquet — the columnar twin, for testing analytics engines (pandas, DuckDB, Spark).

File: PARQUET · Ecommerce · 2,000 rows
Use case: Data engineeringConversion testing· Conversion set

E-commerce Products (CSV, 200 rows)

A realistic e-commerce product catalogue (200 rows) — part of a relational dataset (products, customers, orders) with CSV, JSON, SQL, and Parquet twins for testing joins, imports, and conversion.

File: CSV · Ecommerce · 200 rows
Use case: Data importConversion testing+1· Conversion set

E-commerce Products (JSON, 200 records)

The e-commerce products table as a JSON array — the format twin of the CSV, for import and conversion testing.

File: JSON · Ecommerce · 200 records
Use case: Data importConversion testing· Conversion set

E-commerce Products (Parquet, 200 rows)

The e-commerce products table as Apache Parquet — the columnar twin, for testing analytics engines (pandas, DuckDB, Spark).

File: PARQUET · Ecommerce · 200 rows
Use case: Data engineeringConversion testing· Conversion set

Edge Cases

CSV DST and Leap-Day Timestamps

Timestamps spanning a US spring-forward DST gap and leap-day dates for timezone and calendar edge-case testing.

File: CSV · Edge Cases · 4 rows
Use case: CSV parsingData import

CSV Formula-Injection Safe Sample

A sanitization-test CSV with one equals-prefixed cell clearly labelled sample-only. Use it to verify importers neutralize spreadsheet formulas — not an attack list.

File: CSV · Edge Cases · 2 rows
Use case: CSV parsingError handling

CSV with Duplicate Headers

A small CSV whose header row repeats the column name id — a common importer failure mode.

File: CSV · Edge Cases · 2 rows
Use case: CSV parsingError handling

CSV with Leading-Zero Identifiers

SKU identifiers that start with zeros. Spreadsheet tools often coerce these to numbers and drop the zeros — keep them as text.

File: CSV · Edge Cases · 3 rows
Use case: CSV parsingData import

CSV with Mixed Null Representations

A CSV where missing values are written seven different ways — empty string, NULL, NA, N/A, null, None, and a dash — across text and numeric columns. A fixture for testing null-detection and coercion in CSV importers.

File: CSV · Edge Cases · 8 rows
Use case: CSV parsingError handling+1

CSV with Mixed Timestamp Formats

A CSV listing timestamps in eleven formats — ISO 8601 with Z and numeric offsets, millisecond precision, naive local, date-only, Unix epoch in seconds and milliseconds, US AM/PM, and RFC 1123. A fixture for testing date parsing and timezone normalisation.

File: CSV · Edge Cases · 11 rows
Use case: CSV parsingError handling+1

CSV with Mixed-Type Columns

A CSV whose 'value' column mixes integers, floats, scientific notation, dates, hex, thousands separators, and whitespace, and whose 'flag' column mixes a dozen boolean spellings. A torture test for type inference and schema detection.

File: CSV · Edge Cases · 12 rows
Use case: CSV parsingError handling+1

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

Wide CSV — 1000 Columns

A CSV with 1000 columns and a handful of rows — a stress test for parsers, spreadsheet importers, and databases with column limits or per-row buffering assumptions. Deterministic (fixed seed).

File: CSV · Edge Cases · 5 rows
Use case: CSV parsingPerformance testing+1

Encodings

CSV — Hash Comment Lines

A CSV with # comment lines mixed among data — common in scientific exports; tests comment skipping.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

CSV — ISO-8859-1 (Latin-1)

A Latin-1 CSV with high-bit accented characters — for legacy 8-bit charset detection.

File: CSV · Encodings · 2 rows
Use case: CSV parsingEncoding detection

CSV — Mixed CRLF and LF

A CSV that mixes CRLF and LF row endings within one file — newline normalisation fixture.

File: CSV · Encodings · 3 rows
Use case: CSV parsingEncoding detection

CSV — Pipe Delimiter

A pipe-delimited (| ) tabular file — for testing non-comma delimiter autodetection.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

CSV — Quoted Embedded Newlines

A CSV with a quoted field that contains an embedded newline — a classic RFC 4180 parser stress case.

File: CSV · Encodings · 2 rows
Use case: CSV parsingError handling

CSV — Ragged Column Counts

Rows with differing field counts — for testing how importers pad, truncate, or error on ragged CSV.

File: CSV · Encodings · 3 rows
Use case: CSV parsingError handling

CSV — Semicolon Delimiter (EU)

European-style CSV using semicolons as delimiters and comma decimals — a common locale edge case.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

CSV — Shift-JIS Japanese

A Shift-JIS encoded Japanese CSV — for CJK charset detection and Shift-JIS→UTF-8 conversion in importers.

File: CSV · Encodings · 2 rows
Use case: CSV parsingEncoding detection+1

CSV — Single Column

A one-column CSV of email addresses — edge case for delimiter sniffers that expect commas in every row.

File: CSV · Encodings · 2 rows
Use case: CSV parsingData import

CSV — UTF-16 BE with BOM

UTF-16 big-endian CSV with BOM — for byte-order detection in tabular importers.

File: CSV · Encodings · 3 rows
Use case: CSV parsingEncoding detection

CSV — UTF-16 LE with BOM

The same three data rows as UTF-16 little-endian with a BOM — wide-character CSV decoding fixture.

File: CSV · Encodings · 3 rows
Use case: CSV parsingEncoding detection

CSV — UTF-8 with BOM

A CSV prefixed with a UTF-8 BOM (EF BB BF) and accented / CJK cells — for testing BOM-aware importers.

File: CSV · Encodings · 3 rows
Use case: CSV parsingEncoding detection+1

CSV — Windows-1252 (CP1252)

A CP1252 CSV using the 0x80–0x9F range (smart quotes, euro, bullet) that Latin-1 misreads.

File: CSV · Encodings · 2 rows
Use case: CSV parsingEncoding detection

CSV Extension — Tab Delimited Content

A .csv file whose content is tab-delimited — tests whether importers sniff delimiters or trust the extension.

File: CSV · Encodings · 2 rows
Use case: CSV parsingError handling

Fixed-Width Positions File (TXT)

A classic fixed-width text extract with documented column positions — for COBOL-style / mainframe importer tests.

File: TXT · Encodings · 3 rows
Use case: CSV parsingData import+1

Fake Datasets

Fake Orders Dataset (CSV, 1000 rows)

A 1000-row orders dataset whose user_id references the users dataset — a relational fixture for testing joins and import flows. Paired with a JSON twin.

File: CSV · Fake Datasets · 1,000 rows
Use case: Data importConversion testing· Conversion set

Fake Orders Dataset (JSON, 1000 records)

The 1000-row orders dataset as JSON — the format twin of the CSV version, relational to the users dataset.

File: JSON · Fake Datasets · 1,000 records
Use case: Data importConversion testing· Conversion set

Fake Users Dataset (CSV, 500 rows)

A 500-row dataset of fake but realistic users (name, email, address, date of birth), generated with a fixed seed. Paired with a JSON twin.

File: CSV · Fake Datasets · 500 rows
Use case: Data importConversion testing· Conversion set

Fake Users Dataset (JSON, 500 records)

The 500-row users dataset as a JSON array — the format twin of the CSV version, for testing import and conversion.

File: JSON · Fake Datasets · 500 records
Use case: Data importConversion testing· Conversion set

Feeds

Atom Feed

A well-formed Atom feed with multiple entries — for testing feed readers and parsers.

File: ATOM · Feeds · UTF-8
Use case: Feed parsing

HLS Playlist (M3U8)

An HTTP Live Streaming (HLS) media playlist in UTF-8 M3U8 — #EXT-X-VERSION, target duration, four timed .ts segments, and #EXT-X-ENDLIST — for testing HLS parsers and adaptive-streaming players.

File: M3U8 · Feeds
Use case: Playlist & feed parsingEditor testing

JSON Feed 1.1

A JSON Feed 1.1 document — the JSON alternative to RSS/Atom — with a feed header and three items using content_html, content_text, tags, and publish dates, for testing JSON Feed parsers and readers.

File: JSON · Feeds
Use case: Feed parsingPlaylist & feed parsing+2

M3U Playlist

An extended M3U media playlist with #EXTINF duration and title directives over three track references (local and remote) — for testing playlist parsers and media players.

File: M3U · Feeds
Use case: Playlist & feed parsingEditor testing

OPML Subscription List

An OPML 2.0 subscription list with nested outline groups and three feed entries (title, xmlUrl, htmlUrl) — the format RSS readers use to import and export subscriptions, for testing OPML parsers.

File: OPML · Feeds
Use case: Feed parsingPlaylist & feed parsing+1

RSS 2.0 Feed

A well-formed RSS 2.0 feed with a channel and multiple items — for testing feed readers and parsers.

File: RSS · Feeds · UTF-8
Use case: Feed parsing

Finance

FINANCE — Ledger Lines (CSV)

Synthetic finance dataset (ledger-lines) as CSV — for ETL and warehouse loader tests.

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

FINANCE — Ledger Lines (JSON)

JSON twin of the finance/ledger-lines mini-dataset.

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

Stock OHLCV — Daily Candles (CSV, 252 rows)

A year of daily OHLCV stock candles (open/high/low/close/volume) as a seeded random walk — a realistic finance time-series for testing charting, indicators, and importers. JSON twin included.

File: CSV · Finance · 252 rows
Use case: Data importTime-series data+1· Conversion set

Stock OHLCV — Daily Candles (JSON, 252 records)

The daily OHLCV candles as a JSON array — the format twin of the CSV, for charting and time-series testing.

File: JSON · Finance · 252 records
Use case: Data importTime-series data· Conversion set

Fintech

Fintech Account Balance Snapshot (JSON)

End-of-month account balance snapshot for open-banking API mock tests.

File: JSON · Fintech
Use case: API testing

Fintech Bank Statement Lines (CSV)

Synthetic bank statement line items for reconciliation tooling tests.

File: CSV · Fintech · 2 rows
Use case: Data import

Fintech Double-entry Ledger (JSON)

Balanced double-entry ledger SAMPLE for accounting engine validation tests.

File: JSON · Fintech
Use case: Data importJSON parsing

Fintech FX Rates Time-series (JSON)

Daily USD/EUR SAMPLE rates for FX chart and conversion tests.

File: JSON · Fintech
Use case: Time-series dataJSON parsing

Fintech Payment Intent (JSON)

Stripe-style payment intent SAMPLE JSON for checkout integration tests.

File: JSON · Fintech
Use case: API testing

Fintech SAR Compliance Flag (JSON)

Synthetic suspicious-activity flag JSON for AML compliance workflow tests.

File: JSON · Fintech
Use case: Data import

Fintech Transaction History (CSV)

Synthetic bank transaction history for personal-finance importer tests.

File: CSV · Fintech · 2 rows
Use case: Data importCSV parsing

Geospatial

GeoJSON Sample

A GeoJSON FeatureCollection with a point, a line, and a polygon — for testing map tools and geo importers.

File: GEOJSON · Geospatial · UTF-8
Use case: GeospatialJSON parsing

GPX Track

A GPX track with timestamped trackpoints and elevation — for testing route parsers and mapping tools.

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

KML Places

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

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

World Cities (40 points, GeoJSON)

The same 40 world cities as a GeoJSON FeatureCollection of Points (longitude, latitude order per RFC 7946), each with name, country, and population properties. The mapping twin of the CSV, for testing GeoJSON parsers and map renderers.

File: GEOJSON · Geospatial
Use case: GeospatialData import+1· Conversion set

World Cities (40 rows, CSV)

A curated world-cities dataset — 40 major cities with country, latitude, longitude, and population. A realistic geospatial fixture for testing map plots, geocoding, and CSV→GeoJSON conversion. GeoJSON twin included.

File: CSV · Geospatial · 40 rows
Use case: GeospatialData import+1· Conversion set

Graph

Directed Acyclic Pipeline - GEXF 1.3

A six-stage software pipeline DAG for testing dependency import, cycle checks and reproducible topological sorting. This GEXF 1.3 member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GEXF · Graph
Use case: Graph dataConversion testing+1· Conversion set

Directed Acyclic Pipeline - GraphML

A six-stage software pipeline DAG for testing dependency import, cycle checks and reproducible topological sorting. This GraphML member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GRAPHML · Graph
Use case: Graph dataConversion testing+1· Conversion set

Directed Acyclic Pipeline - JSON edge list

A six-stage software pipeline DAG for testing dependency import, cycle checks and reproducible topological sorting. This JSON edge list member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: JSON · Graph
Use case: Graph dataConversion testing+1· Conversion set

Directed Dependency Cycle - GEXF 1.3

A four-service directed cycle whose only valid topological result is failure, for dependency-analysis regression tests. This GEXF 1.3 member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GEXF · Graph
Use case: Graph dataConversion testing+1· Conversion set

Directed Dependency Cycle - GraphML

A four-service directed cycle whose only valid topological result is failure, for dependency-analysis regression tests. This GraphML member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GRAPHML · Graph
Use case: Graph dataConversion testing+1· Conversion set

Directed Dependency Cycle - JSON edge list

A four-service directed cycle whose only valid topological result is failure, for dependency-analysis regression tests. This JSON edge list member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: JSON · Graph
Use case: Graph dataConversion testing+1· Conversion set

Disconnected Directed Graph - GEXF 1.3

A directed graph with two linked islands and one isolated node, designed for weak-component and isolated-node tests. This GEXF 1.3 member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GEXF · Graph
Use case: Graph dataConversion testing+1· Conversion set

Disconnected Directed Graph - GraphML

A directed graph with two linked islands and one isolated node, designed for weak-component and isolated-node tests. This GraphML member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GRAPHML · Graph
Use case: Graph dataConversion testing+1· Conversion set

Disconnected Directed Graph - JSON edge list

A directed graph with two linked islands and one isolated node, designed for weak-component and isolated-node tests. This JSON edge list member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: JSON · Graph
Use case: Graph dataConversion testing+1· Conversion set

Service Dependency Graph (GraphML, directed)

A directed service-dependency graph in GraphML — ten microservices (web, api, auth, db, cache, queue, worker, …) with their call/dependency edges. A fixture for testing directed-graph importers, cycle detection, and topological sorting.

File: GRAPHML · Graph
Use case: Graph dataData import

Social Network Graph (GEXF)

The same 12-person social network in GEXF 1.3 (Gephi's native format) — node attributes and weighted edges. The format twin of the GraphML file, for testing Gephi imports and GraphML↔GEXF conversion.

File: GEXF · Graph
Use case: Graph dataConversion testing+1· Conversion set

Social Network Graph (GraphML)

A small synthetic social network in GraphML — 12 people in two communities with a few bridging ties, carrying node attributes (name, age, community) and weighted edges. Twinned with a GEXF file for testing graph importers and format converters.

File: GRAPHML · Graph
Use case: Graph dataConversion testing+1· Conversion set

Weighted Directed Multigraph - GEXF 1.3

A weighted acyclic multigraph with two parallel source-to-router edges, checking multiplicity and floating-point weight preservation. This GEXF 1.3 member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GEXF · Graph
Use case: Graph dataConversion testing+1· Conversion set

Weighted Directed Multigraph - GraphML

A weighted acyclic multigraph with two parallel source-to-router edges, checking multiplicity and floating-point weight preservation. This GraphML member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: GRAPHML · Graph
Use case: Graph dataConversion testing+1· Conversion set

Weighted Directed Multigraph - JSON edge list

A weighted acyclic multigraph with two parallel source-to-router edges, checking multiplicity and floating-point weight preservation. This JSON edge list member carries the same node IDs, edge IDs, directions and weights as its two format twins.

File: JSON · Graph
Use case: Graph dataConversion testing+1· Conversion set

Graphql

Sample GraphQL Schema

Sample GraphQL Schema — small deterministic fixture for parsers and the in-browser editor.

File: GRAPHQL · Graphql
Use case: Editor testing

Healthcare

FHIR R4 Patient Bundle (JSON)

A sample HL7 FHIR R4 bundle with a Patient plus vital-sign Observations, an Encounter, and a Condition — a realistic healthcare-interoperability fixture for testing FHIR parsers and mappers. Synthetic data, not a real person.

File: JSON · Healthcare
Use case: Data importConversion testing

Healthcare Claim (FHIR SAMPLE JSON)

Synthetic FHIR Claim resource for healthcare billing parser tests — not a real patient.

File: JSON · Healthcare
Use case: Data importJSON parsing

Healthcare Eligibility Response (JSON)

Fictional insurance eligibility check response for prior-auth workflow tests.

File: JSON · Healthcare
Use case: API testingJSON parsing

Healthcare Lab Results (CSV)

Synthetic lab result rows for clinical data warehouse import tests.

File: CSV · Healthcare · 2 rows
Use case: Data importCSV parsing

Healthcare ORM HL7 Message (SAMPLE)

Sample HL7 v2 ORM order message with PID and OBR segments — fictional patient and order ids.

File: HL7 · Healthcare
Use case: Data import

Healthcare Patient Demographics (CSV)

Synthetic patient demographics CSV for EHR import and de-identification pipeline tests.

File: CSV · Healthcare · 2 rows
Use case: Data importCSV parsing

Healthcare Prescription (JSON)

Synthetic e-prescription JSON for pharmacy routing and validation tests.

File: JSON · Healthcare
Use case: Data import

Healthcare Procedure Codes (JSON)

SAMPLE procedure code list with fees for medical billing calculator tests.

File: JSON · Healthcare
Use case: Data importJSON parsing

Hr

Employee Directory (CSV, 30 rows)

An employee directory — 30 staff with department, title, hire date, salary, and manager reference. Synthetic HR data for testing org-chart builders, directory imports, and payroll pipelines.

File: CSV · Hr · 30 rows
Use case: Data importConversion testing· Conversion set

Employee Directory (JSON, 30 records)

The employee directory as a JSON array — the format twin of the CSV, for HR import testing.

File: JSON · Hr · 30 records
Use case: Data importConversion testing· Conversion set

HR — Employees Mini (CSV)

Synthetic hr dataset (employees-mini) as CSV — for ETL and warehouse loader tests.

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

HR — Employees Mini (JSON)

JSON twin of the hr/employees-mini mini-dataset.

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

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

Inventory

Inventory BOM Multi-level (JSON)

Multi-level bill-of-materials SAMPLE for MRP and assembly planning tests.

File: JSON · Inventory
Use case: Data importJSON parsing

Inventory Cycle Count (CSV)

Cycle-count variance SAMPLE for inventory audit reconciliation tests.

File: CSV · Inventory · 1 row
Use case: Data importCSV parsing

Inventory Purchase Order (JSON)

Synthetic purchase order JSON for procurement workflow tests.

File: JSON · Inventory
Use case: Data import

Inventory SKU Catalog (CSV)

Fictional SKU catalog for ERP and POS import tests.

File: CSV · Inventory · 2 rows
Use case: Data importCSV parsing

Inventory Stock Levels (CSV)

Per-warehouse stock quantities for inventory reconciliation tests.

File: CSV · Inventory · 2 rows
Use case: Data import

Inventory Warehouse Locations (JSON)

Warehouse and bin metadata for WMS routing tests.

File: JSON · Inventory
Use case: JSON parsing

Iot

IOT — Sensor Readings Mini (CSV)

Synthetic iot dataset (sensor-readings-mini) as CSV — for ETL and warehouse loader tests.

File: CSV · Iot · 12 rows
Use case: Data importCSV parsing· Conversion set

IOT — Sensor Readings Mini (JSON)

JSON twin of the iot/sensor-readings-mini mini-dataset.

File: JSON · Iot · 12 records
Use case: Data importJSON parsing· Conversion set

IoT Sensor Readings (CSV, 1440 rows)

A day of IoT sensor readings (temperature, humidity, pressure) at one-minute intervals from three sensors, with a realistic daily cycle plus noise — for testing time-series ingestion and downsampling. JSON twin included.

File: CSV · Iot · 1,440 rows
Use case: Data importTime-series data+1· Conversion set

IoT Sensor Readings (JSON, 1440 records)

The IoT sensor readings as a JSON array — the format twin of the CSV, for time-series testing.

File: JSON · Iot · 1,440 records
Use case: Data importTime-series data· Conversion set

JSON

Deeply Nested JSON

A deeply nested JSON document with objects inside arrays inside objects — for testing recursive parsing and path access.

File: JSON · JSON
Use case: JSON parsing

Flat JSON Array

A flat JSON array of ten simple objects — the baseline case for JSON parsing and mapping.

File: JSON · JSON · 10 records
Use case: JSON parsingData import

Intentionally Invalid JSON

An intentionally invalid JSON file with a trailing comma and a missing closing brace — for testing parser error handling and messages. Not valid JSON by design.

File: JSON · JSON
Use case: JSON parsingError handling

JSON Lines (JSONL)

A JSON Lines file with one object per line — for testing streaming/newline-delimited JSON parsers.

File: JSONL · JSON · 10 records
Use case: JSON parsingData import

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

NDJSON Stream

A newline-delimited JSON (NDJSON) stream of event records — for testing streaming JSON parsers.

File: NDJSON · JSON · 4 records
Use case: JSON parsingData import

Lab

Lab Measurements (CSV)

Synthetic lab readings (temperature, pressure, pH) with ISO timestamps for scientific ETL tests. CSV twin.

File: CSV · Lab · 16 rows
Use case: Data importCSV parsing· Conversion set

Lab Measurements (JSON)

Synthetic lab readings (temperature, pressure, pH) with ISO timestamps for scientific ETL tests. JSON twin.

File: JSON · Lab · 16 records
Use case: Data importJSON parsing· Conversion set

Large

Large Transactions Dataset (CSV, 50k rows)

A 50,000-row transactions dataset — an in-repo 'large' fixture for testing streaming CSV parsers, import performance, and pagination. Deterministic (fixed seed).

File: CSV · Large · 50,000 rows
Use case: Data importPerformance testing+1

Logs

Apache Access Log — Combined Format (log)

An Apache access log in the Combined Log Format — the Common fields plus referer and user-agent. A realistic web-server log for testing access-log parsers, analytics, and grok patterns.

File: LOG · Logs
Use case: Log parsingData import+1· Conversion set

Apache Access Log — Common Format (log)

An Apache access log in the Common Log Format (CLF) — client, timestamp, request line, status, and byte count. Deterministic, with reserved documentation IPs. Paired with a Combined-format twin for testing log parsers.

File: LOG · Logs
Use case: Log parsingData import+1· Conversion set

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

Java Stack Trace (log)

A realistic Java stack trace — a Spring-style NullPointerException with a nested 'Caused by' chain and '... N more' elision. A fixture for testing stack-trace parsers, error groupers, and log viewers.

File: LOG · Logs · 8 frames
Use case: Log parsingError handling· Conversion set

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

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

Log Sample — App Json Structured

Tiny SAMPLE log excerpt (app-json-structured) for parser and alert-rule tests.

File: LOG · Logs
Use case: Log parsingError handling· Conversion set

Log Sample — Cloudflare Ray Sample

Tiny SAMPLE log excerpt (cloudflare-ray-sample) for parser and alert-rule tests.

File: LOG · Logs
Use case: Log parsingError handling· Conversion set

Log Sample — Multiline Stacktrace

Tiny SAMPLE log excerpt (multiline-stacktrace) for parser and alert-rule tests.

File: LOG · Logs
Use case: Log parsingError handling· Conversion set

Log Sample — Nginx Access Sample

Tiny SAMPLE log excerpt (nginx-access-sample) for parser and alert-rule tests.

File: LOG · Logs
Use case: Log parsingError handling· Conversion set

Log Sample — Nginx Error Sample

Tiny SAMPLE log excerpt (nginx-error-sample) for parser and alert-rule tests.

File: LOG · Logs
Use case: Log parsingError handling· Conversion set

Log Sample — Systemd Journal Excerpt

Tiny SAMPLE log excerpt (systemd-journal-excerpt) for parser and alert-rule tests.

File: LOG · Logs
Use case: Log parsingError handling· Conversion set

Nginx Access Log

An nginx combined-format access log with several requests, including a 403 and a 404 — for testing log parsers.

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

Node.js Stack Trace (log)

A realistic Node.js/Express stack trace — a TypeError with V8-style 'at function (file:line:col)' frames including an async frame and internal node: frames. A fixture for testing JS stack-trace parsers.

File: LOG · Logs · 7 frames
Use case: Log parsingError handling· Conversion set

Python Traceback (log)

A realistic Python traceback with a chained exception ('During handling of the above exception...') and a caret error indicator. A fixture for testing traceback parsers and error-reporting tools.

File: LOG · Logs · 4 frames
Use case: Log parsingError handling· Conversion set

Structured Log — logfmt (log)

A structured application log in logfmt — space-separated key=value pairs (ts, level, msg, method, path, status, duration, request_id) as used by many Go and Heroku-style services. A fixture for testing logfmt parsers.

File: LOG · Logs
Use case: Log parsingObservability

Syslog Messages — RFC 3164 (log)

A BSD-style syslog (RFC 3164) sample — timestamp, host, process and PID, then the message, across sshd, cron, kernel, nginx, and application entries. A fixture for testing syslog parsers and forwarders.

File: LOG · Logs
Use case: Log parsingObservability

Marketing

Marketing Attribution (CSV)

Synthetic multi-touch attribution click rows with UTM fields — for marketing analytics importers. CSV twin.

File: CSV · Marketing · 10 rows
Use case: Data importCSV parsing· Conversion set

Marketing Attribution (JSON)

Synthetic multi-touch attribution click rows with UTM fields — for marketing analytics importers. JSON twin.

File: JSON · Marketing · 10 records
Use case: Data importJSON parsing· Conversion set

Notebooks

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

P8 Convert

Convert v2 ORC Employee Table Source

Binary orc source for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-source.

File: ORC · P8 Convert · 5 rows
Use case: Conversion testingData engineering+1· Conversion set

Convert v2 ORC Expected CSV

Csv semantic reference for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-csv.

File: CSV · P8 Convert · 5 rows
Use case: Conversion testingData engineering+1· Conversion set

Convert v2 ORC Expected JSON

Json semantic reference for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-json.

File: JSON · P8 Convert · 5 rows
Use case: Conversion testingData engineering+1· Conversion set

Convert v2 Protobuf Creator Record

Valid Protobuf wire record with string, uint32, and string fields for schema-guided decoding. Stable P8 artifact p8-convert-protobuf-source.

File: PB · P8 Convert · 3 fields
Use case: Conversion testingSerialization testing+1· Conversion set

Convert v2 Protobuf Expected JSON

Expected JSON semantic result for the schema-guided Protobuf decode. Stable P8 artifact p8-convert-protobuf-expected.

File: JSON · P8 Convert · 3 fields
Use case: Conversion testingSerialization testing+1· Conversion set

Convert v2 Protobuf Missing-Schema Controlled Failure

Valid wire bytes intentionally supplied without a matching schema so tools must preserve unknown field 15. Stable P8 artifact p8-convert-protobuf-missing-schema.

File: PB · P8 Convert · 1 field
Use case: Conversion testingSerialization testing+1· Conversion set

Convert v2 Protobuf Schema Companion

Proto3 schema companion declaring the three fields used by the binary creator record. Stable P8 artifact p8-convert-protobuf-schema.

File: PROTO · P8 Convert · 3 fields
Use case: Conversion testingSerialization testing+1· Conversion set

Pos

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

Protobuf

Sample Protobuf Schema

Sample Protobuf Schema — small deterministic fixture for parsers and the in-browser editor.

File: PROTO · Protobuf
Use case: Editor testing

Real Estate

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

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

Saas

SaaS Product Events (CSV)

Synthetic product-analytics events (signup/login/upgrade) for testing event pipelines and warehouse loads. CSV twin.

File: CSV · Saas · 24 rows
Use case: Data importCSV parsing· Conversion set

SaaS Product Events (JSON)

Synthetic product-analytics events (signup/login/upgrade) for testing event pipelines and warehouse loads. JSON twin.

File: JSON · Saas · 24 records
Use case: Data importJSON parsing· Conversion set

Schema

Avro Schema Evolution - Backward-Compatible

The compatible Avro record schema for reader/writer compatibility tests. Backward compatible for old records: nullable email is added with a null default.

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

Avro Schema Evolution - Baseline

The baseline Avro record schema for reader/writer compatibility tests. Reference writer schema: id and name are strings.

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

Avro Schema Evolution - Breaking

The breaking Avro record schema for reader/writer compatibility tests. Breaking relative to baseline: id changes to long and tenantId has no default.

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

Event JSON Schema

Draft-07 JSON Schema describing a SAMPLE event object for domain-specific validator tests.

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

Invalid JSON Schema — Json Schema Bad Ref

Intentionally invalid JSON Schema (json-schema-bad-ref) for negative validator tests.

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

Invalid JSON Schema — Json Schema Empty Object

Intentionally invalid JSON Schema (json-schema-empty-object) for negative validator tests.

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

Invalid JSON Schema — Json Schema Missing Type

Intentionally invalid JSON Schema (json-schema-missing-type) for negative validator tests.

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

Invalid OpenAPI — Openapi Broken Ref

OpenAPI with a response schema $ref pointing at a missing component — tests broken-reference detection.

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

Invalid OpenAPI — Openapi Missing Paths

OpenAPI document with paths set to null — intentionally invalid for negative schema tests.

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

Invalid OpenAPI — Openapi Wrong Version

OpenAPI with an unsupported openapi version string — negative case for version validators.

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

Inventory Item JSON Schema

Draft-07 JSON Schema describing a SAMPLE inventory item object for domain-specific validator tests.

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

Invoice JSON Schema

Draft-07 JSON Schema describing a SAMPLE invoice object for domain-specific validator tests.

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

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

OpenAPI 3.1 Webhooks Section (YAML)

Minimal OpenAPI 3.1 document with a webhooks section — for testing webhook-aware spec parsers.

File: YAML · Schema
Use case: Schema / OpenAPI testingAPI testing

OpenAPI Components-only Document (JSON)

OpenAPI document with empty paths but populated components — tests partial spec loaders.

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

Openapi Request Create Pet

Sample POST /pets request body matching the pet-store OpenAPI spec.

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

Openapi Response Created

Sample 201 created pet response body for contract testing.

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

Openapi Response Not Found

Sample 404 problem response for OpenAPI error-handling tests.

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

Openapi Response Pet Page

Sample paginated pet list response for mock-server and contract tests.

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

OpenAPI Schema Evolution - Backward-Compatible

The compatible member of a complete OpenAPI 3.1 ticket endpoint contract. Backward compatible: an optional priority response property is added and existing operations stay unchanged.

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

OpenAPI Schema Evolution - Baseline

The baseline member of a complete OpenAPI 3.1 ticket endpoint contract. Reference API: string ticket IDs and required id/summary response properties.

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

OpenAPI Schema Evolution - Breaking

The breaking member of a complete OpenAPI 3.1 ticket endpoint contract. Breaking relative to baseline: ticket id becomes integer and status becomes a required response property.

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

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

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

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

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

Protocol Buffers Schema Evolution - Baseline

The baseline proto3 Customer message for field-number and wire-compatibility testing. Reference wire contract: field 1 is string id and field 2 is string name.

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

Protocol Buffers Schema Evolution - Breaking

The breaking proto3 Customer message for field-number and wire-compatibility testing. Breaking relative to baseline: field number 2 is reused with a different name and wire type.

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

User Instance — Invalid (5 violations)

User JSON deliberately violating the schema five ways — negative case for validator error reporting.

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

User Instance — Valid

JSON instance conforming to the Wave F user JSON Schema — positive validator test case.

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

User JSON Schema (draft 2020-12)

Draft 2020-12 JSON Schema for a user object with email format and role enum — paired with valid/invalid instances.

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

Scientific

BibTeX Bibliography (.bib)

A BibTeX bibliography with three real citations (Lovelace, Knuth, Shannon) across article, book, and inproceedings types — for testing BibTeX parsers, reference managers, and citation converters.

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

FITS Image (.fits)

A minimal but valid FITS image — a primary header of 80-character cards padded to a 2880-byte block, followed by a 16x16 unsigned-byte pixel gradient — for testing FITS readers and header-card parsers.

File: FITS · Scientific
Use case: Scientific data

MDL Molfile — Water (.mol)

An MDL Molfile (V2000) of a water molecule with standard geometry — a counts line, atom block with 2D coordinates, and bond block — for testing cheminformatics parsers and MOL/SDF converters.

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

NetCDF Gridded Data (.nc)

A NetCDF-3 (classic) file holding a small CF-convention gridded temperature field over latitude, longitude, and time, with named dimensions and units — for testing NetCDF readers like netCDF4 and xarray.

File: NC · Scientific
Use case: Scientific data

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

RIS Citations (.ris)

The same three references as an RIS citation file with two-letter tags and ER record terminators — the twin of the BibTeX file, for testing RIS import and BibTeX/RIS conversion.

File: RIS · Scientific · 3 records
Use case: Scientific dataEditor testing· Conversion set

Security

Certificate Signing Request (CSR)

A PKCS#10 certificate signing request (PEM) with the subject and SAN, self-signed by the RSA key to prove key possession — for testing CSR parsers and certificate-authority intake flows.

File: CSR · Security
Use case: Certificate & key testingEditor testing

Ed25519 Private Key (PEM)

An Ed25519 private key in PKCS#8 PEM, derived from a fixed seed — a published, sample-only modern elliptic-curve key for testing PEM parsers and Ed25519 tooling. Never use it for real.

File: KEY · Security
Use case: Certificate & key testingEditor testing

htpasswd (HTTP Basic Auth)

An Apache/nginx .htpasswd file with two users hashed using the {SHA} scheme (Base64 SHA-1) — the sample passwords are documented in the file, for testing Basic-Auth credential parsers and hash identification.

File: HTPASSWD · Security
Use case: Certificate & key testingEditor testing

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

RSA 2048 Private Key (PEM)

A 2048-bit RSA private key in unencrypted PKCS#8 PEM — a deliberately PUBLISHED, sample-only key for testing PEM key parsers and PKCS#8 decoders. Never use it for anything real.

File: KEY · Security
Use case: Certificate & key testingEditor testing

Sample JWT — Decoded (JSON)

The decoded header and payload of the sample JWT as JSON, alongside the public signing secret and algorithm — the ground truth for checking a JWT decoder's output.

File: JSON · Security
Use case: JSON parsingEditor testing· Paired fixture

Sample JWT (HS256)

A sample JSON Web Token (JWT) signed with HS256 using a published example secret — verifiable but powerless — for testing JWT decoders and validators. Sample only, never for production. Paired with its decoded claims.

File: JWT · Security
Use case: Conversion testingEditor testing· Paired fixture

SSH Public Key (Ed25519)

An OpenSSH-format Ed25519 public key (the shareable half of the key pair) — a single line of algorithm, Base64 key blob, and comment, for testing SSH public-key parsers and authorized_keys tooling.

File: PUB · Security
Use case: Certificate & key testingEditor testing

X.509 Certificate (.crt)

The same self-signed certificate under the conventional .crt extension (PEM-encoded) — for testing trust-store importers and tools that key off the .crt extension. Sample only.

File: CRT · Security
Use case: Certificate & key testingEditor testing· Conversion set

X.509 Certificate (DER)

The binary DER encoding of the same certificate — for testing ASN.1/DER parsers, Java keystores, and DER-to-PEM converters. Published sample certificate, not a real identity.

File: DER · Security
Use case: Certificate & key testingEditor testing· Conversion set

X.509 Certificate (PEM)

A self-signed X.509 v3 certificate in PEM (Base64) encoding with a SAN and key-usage extensions — published sample material for testing certificate and TLS parsers. Not a real identity.

File: PEM · Security
Use case: Certificate & key testingEditor testing· Conversion set

Sports

Sports League Standings (CSV)

A football-style league table — position, played, won/drawn/lost, goals for/against, goal difference, and points for ten teams, derived from a full round of synthetic match results. Paired with the results JSON.

File: CSV · Sports
Use case: Data importConversion testing· Conversion set

Sports Match Results (JSON)

The full round of match results behind the league table — home/away teams, scores, and dates as a JSON array. A fixture for testing sports-data importers and standings calculators.

File: JSON · Sports
Use case: Data importConversion testing· Conversion set

Sql

MySQL SQL Dump

A MySQL-flavour SQL dump with backtick-quoted identifiers and engine options — for testing SQL importers.

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

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

Star Schema

Star Schema — Customer Dimension (CSV)

The customer dimension of a star schema — surrogate key, name, city, country, and segment. Joins to the sales fact table on customer_key. Names are synthetic.

File: CSV · Star Schema · 40 rows
Use case: Data importData engineering+1· Conversion set

Star Schema — Date Dimension (CSV)

The date dimension of a star schema — one row per day with a YYYYMMDD surrogate key and calendar attributes (year, quarter, month, weekday). Joins to the sales fact table on date_key.

File: CSV · Star Schema · 31 rows
Use case: Data importData engineering+1· Conversion set

Star Schema — Product Dimension (CSV)

The product dimension of a star schema — surrogate key, SKU, name, category, and unit price. Joins to the sales fact table on product_key.

File: CSV · Star Schema · 20 rows
Use case: Data importData engineering+1· Conversion set

Star Schema — Sales Fact Table (CSV, 300 rows)

The sales fact table at the centre of a star schema — 300 sale lines with foreign keys to the date, product, and customer dimensions plus quantity and amount measures. A fixture for testing joins, star-schema imports, and BI tools.

File: CSV · Star Schema · 300 rows
Use case: Data importData engineering+1· Conversion set

Support

SUPPORT — Tickets (CSV)

Synthetic support dataset (tickets) as CSV — for ETL and warehouse loader tests.

File: CSV · Support · 6 rows
Use case: Data importCSV parsing· Conversion set

SUPPORT — Tickets (JSON)

JSON twin of the support/tickets mini-dataset.

File: JSON · Support · 6 records
Use case: Data importJSON parsing· Conversion set

Surveys

Survey Responses — Likert + NPS (CSV, 60 rows)

A customer-survey response set — 60 respondents rating five statements on a 1–5 Likert scale plus a 0–10 NPS score and a segment. A fixture for testing survey analysis, aggregation, and NPS/CSAT calculations.

File: CSV · Surveys · 60 rows
Use case: Data importConversion testing+1

Synth

Synth Batch 01 (CSV)

Deterministic synthetic CSV batch 01 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 01 (JSON)

Deterministic synthetic JSON batch 01 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 02 (CSV)

Deterministic synthetic CSV batch 02 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 02 (JSON)

Deterministic synthetic JSON batch 02 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 03 (CSV)

Deterministic synthetic CSV batch 03 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 03 (JSON)

Deterministic synthetic JSON batch 03 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 04 (CSV)

Deterministic synthetic CSV batch 04 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 04 (JSON)

Deterministic synthetic JSON batch 04 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 05 (CSV)

Deterministic synthetic CSV batch 05 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 05 (JSON)

Deterministic synthetic JSON batch 05 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 06 (CSV)

Deterministic synthetic CSV batch 06 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 06 (JSON)

Deterministic synthetic JSON batch 06 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 07 (CSV)

Deterministic synthetic CSV batch 07 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 07 (JSON)

Deterministic synthetic JSON batch 07 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 08 (CSV)

Deterministic synthetic CSV batch 08 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 08 (JSON)

Deterministic synthetic JSON batch 08 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 09 (CSV)

Deterministic synthetic CSV batch 09 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 09 (JSON)

Deterministic synthetic JSON batch 09 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 10 (CSV)

Deterministic synthetic CSV batch 10 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 10 (JSON)

Deterministic synthetic JSON batch 10 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 11 (CSV)

Deterministic synthetic CSV batch 11 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 11 (JSON)

Deterministic synthetic JSON batch 11 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 12 (CSV)

Deterministic synthetic CSV batch 12 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 12 (JSON)

Deterministic synthetic JSON batch 12 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 13 (CSV)

Deterministic synthetic CSV batch 13 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 13 (JSON)

Deterministic synthetic JSON batch 13 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 14 (CSV)

Deterministic synthetic CSV batch 14 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 14 (JSON)

Deterministic synthetic JSON batch 14 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 15 (CSV)

Deterministic synthetic CSV batch 15 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 15 (JSON)

Deterministic synthetic JSON batch 15 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 16 (CSV)

Deterministic synthetic CSV batch 16 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 16 (JSON)

Deterministic synthetic JSON batch 16 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 17 (CSV)

Deterministic synthetic CSV batch 17 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 17 (JSON)

Deterministic synthetic JSON batch 17 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 18 (CSV)

Deterministic synthetic CSV batch 18 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 18 (JSON)

Deterministic synthetic JSON batch 18 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 19 (CSV)

Deterministic synthetic CSV batch 19 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 19 (JSON)

Deterministic synthetic JSON batch 19 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Synth Batch 20 (CSV)

Deterministic synthetic CSV batch 20 for bulk-import smoke tests.

File: CSV · Synth · 5 rows
Use case: Data importCSV parsing· Conversion set

Synth Batch 20 (JSON)

Deterministic synthetic JSON batch 20 for bulk-import smoke tests.

File: JSON · Synth · 5 records
Use case: Data importJSON parsing· Conversion set

Timeseries

Time-series — Business Hours

Hourly order counts weekdays only (09–16 UTC) across three SAMPLE days.

File: CSV · Timeseries · 24 rows
Use case: Time-series dataData import+1

Time-series — DST Fall Back Duplicate Hour (CSV)

Load readings with a repeated 01:00 local hour on fall-back DST — tests ambiguous timestamp handling.

File: CSV · Timeseries · 5 rows
Use case: Time-series dataData import+1

Time-series — DST Spring Forward Gap (CSV)

Hourly load data skipping the 03:00 hour on DST spring-forward day — tests timezone/DST gap handling.

File: CSV · Timeseries · 4 rows
Use case: Time-series dataData import+1

Time-series — Duplicate Timestamp Keys (CSV)

Two rows share the same timestamp key — tests deduplication and last-write-wins policies.

File: CSV · Timeseries · 3 rows
Use case: Time-series dataData import+2· Conversion set

Time-series — Duplicate Timestamp Keys (JSON)

JSON array with duplicate timestamp keys for ingestion pipeline tests.

File: JSON · Timeseries · 3 records
Use case: Time-series dataData import+1· Conversion set

Time-series — Epoch Boundary

Timestamps at Unix epoch and classic 32-bit Y2038 boundary.

File: JSON · Timeseries · 2 rows
Use case: Time-series dataData import+1

Time-series — Gap Filled

Series with an explicit null value at a missing sample point.

File: CSV · Timeseries · 3 rows
Use case: Time-series dataData import+1

Time-series — Irregular Intervals (CSV)

Sensor readings at irregular minute gaps — tests time-series resampling and gap detection.

File: CSV · Timeseries · 8 rows
Use case: Time-series dataData import+1· Conversion set

Time-series — Irregular Intervals (JSON)

JSON twin of irregular-interval sensor readings for charting library tests.

File: JSON · Timeseries · 8 records
Use case: Time-series dataData import+1· Conversion set

Time-series — Leap Day

Readings spanning Feb 29 leap day — calendar edge case.

File: CSV · Timeseries · 2 rows
Use case: Time-series dataData import+1

Time-series — Millisecond

Sub-second millisecond timestamps for precision parsing tests.

File: JSON · Timeseries · 2 rows
Use case: Time-series dataData import+1

Time-series — Mixed Tz

Same nominal instant expressed in Z, -05:00, and +09:00 offsets.

File: JSON · Timeseries · 3 rows
Use case: Time-series dataData import+1

Time-series — Nan Gaps

CSV with NaN string and empty cells representing missing measurements.

File: CSV · Timeseries · 3 rows
Use case: Time-series dataData import+1

Time-series — Out Of Order

Timestamps out of chronological order — tests sort-on-ingest behaviour.

File: CSV · Timeseries · 3 rows
Use case: Time-series dataData import+1

Time-series — Sparse Events (JSONL)

Sparse event log in JSON Lines — two events hours apart for event-stream ingestion tests.

File: JSONL · Timeseries · 2 records
Use case: Time-series dataData import+2

Time-series — Weekly Agg

Pre-aggregated weekly totals JSON for rollup/chart tests.

File: JSON · Timeseries · 1 row
Use case: Time-series dataData import+1

Travel

Flight Schedule (CSV, 30 rows)

A flight-schedule dataset — 30 flights with airline, origin/destination airports, departure/arrival times, aircraft, gate, and status. Synthetic data for testing travel apps, schedule parsers, and status boards.

File: CSV · Travel · 30 rows
Use case: Data importConversion testing· Conversion set

Flight Schedule (JSON, 30 records)

The flight schedule as a JSON array — the format twin of the CSV, for import and display tests.

File: JSON · Travel · 30 records
Use case: Data importConversion testing· Conversion set

Weather

Weather Forecast — 30 days (CSV, 30 rows)

A 30-day daily weather forecast for one city — high/low temperature, condition, precipitation, wind, and humidity. Synthetic (seeded) data for testing weather widgets, chart tools, and time-series import.