Explore the test library

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

Filter the library

SearchTypeCategorySubcategoryFormatUse caseIndustryWorkflowValidityEditable workspaceDestination platformBrowser test targetSort

5297 results

Page 152 of 221; 24 results per page.

Show the canonical directory

Press Release: Showroom (HTML, SAMPLE)

HTML twin of the SAMPLE showroom press release.

File: HTML · Press Release
Use case: TemplatesEditor testing· Conversion set

Press Release: Showroom (Markdown, SAMPLE)

Markdown twin of the SAMPLE showroom press release.

File: MD · Press Release
Use case: TemplatesEditor testing· Conversion set

Press Release: Showroom (PDF, SAMPLE)

PDF twin of the SAMPLE showroom press release.

File: PDF · Press Release
Use case: TemplatesPDF editor testing· Conversion set

Privacy Policy Deep (DOCX, SAMPLE)

DOCX twin of the deep SAMPLE privacy policy.

File: DOCX · Privacy Policy
Use case: TemplatesPrivacy export testing· Conversion set

Privacy Policy Deep (HTML, SAMPLE)

HTML twin of the deep SAMPLE privacy policy.

File: HTML · Privacy Policy
Use case: TemplatesPrivacy export testing+1· Conversion set

Privacy Policy Deep (Markdown, SAMPLE)

Deeper SAMPLE privacy policy in Markdown with purposes table and rights, not legal advice.

File: MD · Privacy Policy
Use case: TemplatesPrivacy export testing+1· Conversion set

Privacy Policy Deep (PDF, SAMPLE)

PDF twin of the deep SAMPLE privacy policy.

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

Privacy Policy Template (Markdown, SAMPLE)

A short fictional privacy policy in Markdown, for template and content-pipeline tests.

File: MD · Privacy Policy
Use case: TemplatesEditor testing+1

PRJ: UTM Zone 28N (EPSG:32628) in WKT 1

The UTM zone that actually contains the invented territory: zone 28N, central meridian 15 W. It is a definition fixture only: no projected coordinates are published for it here, because a transverse Mercator value is not something to take on trust from a fixture.

File: PRJ · Crs
Use case: GeospatialConversion testing+1· Conversion set

PRJ: Web Mercator (EPSG:3857) in WKT 1

The projection every web map uses, defined as Esri's Mercator_Auxiliary_Sphere. It treats the ellipsoid as a sphere for the projection maths while keeping ellipsoidal latitudes, which is why it is a pseudo-Mercator and why it cannot represent latitudes beyond about 85.05 degrees.

File: PRJ · Crs
Use case: GeospatialConversion testing+1· Conversion set

PRJ: WGS 84 Geographic in WKT 1 (Esri flavour)

The reference .prj for this category: WGS 84 geographic in Esri's WKT 1 dialect, which uses D_WGS_1984 and GCS_WGS_1984 in place of the OGC spellings and carries no AUTHORITY node. Everything else in this family is a variation on it.

File: PRJ · Crs
Use case: GeospatialConversion testing+1· Conversion set

PRJ: WGS 84 in WKT 2 (2019)

The same CRS in WKT 2, which renames almost every keyword (GEOGCRS, ELLIPSOID, LENGTHUNIT) and (crucially) declares axis order explicitly with AXIS and ORDER. WKT 1 left that implicit, which is the root of most latitude/longitude swaps.

File: PRJ · Crs
Use case: GeospatialConversion testing+1· Conversion set

PRJ: World Equidistant Cylindrical (EPSG:4087) in WKT 1

Plate carrée on a sphere of radius 6,378,137 m: the simplest projection with a closed form you can check by hand. That is exactly why it is here: it makes the reprojection pair in this subcategory verifiable with a calculator rather than a library.

File: PRJ · Crs
Use case: GeospatialConversion testing+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

Product Return RMA AcroForm (SAMPLE)

A one-page fillable PDF twin of the product return rma HTML form. Its canonical AcroForm field tree, widgets, values, and appearance streams are generator-validated.

File: PDF · Retail Returns · 1 page
Use case: Form testingForm parsing+1· Conversion set

Product Return RMA Field Manifest (JSON)

Machine-readable field names, labels, types, required states, choices, and input hints for the product return rma family.

File: JSON · Retail Returns · 8 fields
Use case: Form testingForm parsing+1· Conversion set

Product Return RMA Form (HTML)

A product-return authorization request for testing commerce intake, order and SKU matching, condition codes, quantities, and requested-resolution workflows. This standalone HTML reference works offline, uses explicit labels and native validation, and submits nowhere.

File: HTML · Retail Returns · 8 fields
Use case: Form testingForm parsing+1· Conversion set

Product Return RMA Sample Export (CSV)

A one-row UTF-8 CSV export of the fictional product return rma response with columns in the same order as the field manifest.

File: CSV · Retail Returns · 1 row
Use case: Form testingForm parsing+1· Conversion set

Product Return RMA Sample Response (JSON)

Fictional submitted values for every documented product return rma field, suitable for request parsing, mapping, and round-trip tests.

File: JSON · Retail Returns · 8 fields
Use case: Form testingForm parsing+1· Conversion set

txt

13.5 KB

Profile: 200-Frame Recursive Stack (txt)

A recursive-descent parser profiled mid-recursion: stacks up to 204 frames deep where one frame repeats 200 times, on lines over 3,000 characters. Flamegraph renderers with a fixed depth limit truncate this silently, and line-length limits split it into nonsense.

File: TXT · Profiles
Use case: ObservabilityPerformance testing+1· Conversion set

txt

618 B

Profile: Demangled Symbols That Break the Folded Format (txt)

Demangled C++ templates, Rust trait impls, Java generics, lambdas and unresolved hex addresses in the folded format, including one symbol containing a semicolon, which the format has no way to escape. That line is genuinely ambiguous, and how a parser handles it is the point.

File: TXT · Profiles
Use case: ObservabilityLog parsing+1· Conversion set

Progressive JPEG

The same photo as a progressive JPEG (loads coarse-to-fine): the twin of the baseline JPEG, for testing progressive decoding and byte-order handling.

File: JPG · Color And Metadata · 512 × 512 px
Use case: Compression testingImage pipeline QA· Paired fixture