Explore the test library

Find files, editable templates and browser test targets by what you need to make or test. The directory below is cut by format; the two collections under it cut the same library by subject and by workflow.

Filter the library

SearchTypeCategorySubcategoryFormatUse caseIndustryWorkflowValidityEditable workspaceDestination platformBrowser test targetSort

8584 results

Page 353 of 358; 24 results per page.

Show the canonical directory

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 (.crt): Security SAMPLE

Same SAMPLE certificate as .crt (PEM bytes) for tools that expect the CRT extension.

File: CRT · Pki · PEM-as-CRT
Use case: Certificate & key 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 (DER): Security SAMPLE

DER-encoded twin of the Wave G SAMPLE certificate for binary X.509 decoders.

File: DER · Pki · DER
Use case: Certificate & key 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

X.509 Certificate (PEM): Security SAMPLE

Self-signed X.509 SAMPLE certificate in PEM under /files/security/, published sample material for TLS and PEM parsers.

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

X.509 Certificate Chain (PEM): SAMPLE

Two-PEM-block SAMPLE chain file for multi-cert parsers and bundle importers.

File: PEM · Pki · PEM
Use case: Certificate & key testing

X12 837 claim batch: Juniper Fitness and Clinic Administration

X12 837 professional claim batch for Juniper Fitness and Clinic Administration. One interchange, one functional group, one transaction set carrying all 16 claims and 18 service lines. The SE segment declares 225 segments from ST to SE inclusive, which is the count a receiver checks first. Every CLM02 equals the SV102 amounts below it, and the CLM02 values sum to 1,180.00 USD. Segments are terminated with a tilde and the file uses CRLF line endings, which is what an X12 interchange carries in practice.

File: EDI · Healthcare Claims
Use case: Data importSchema validation· Conversion set

X12 837 single claim: Juniper Fitness and Clinic Administration

X12 837 professional claim, single claim for Juniper Fitness and Clinic Administration. The same interchange structure carrying one claim, CLM-0006, with 2 service lines of 120.00 and 85.00 USD. CLM02 is 205.00, which is exactly those two SV102 amounts added. SE01 declares 27 segments.

File: EDI · Healthcare Claims
Use case: Data importSchema validation· Paired fixture

X12 EDI 204: SAMPLE

Short ANSI X12 204 SAMPLE transaction for EDI parser / translator tests.

File: EDI · Hl7 Edi
Use case: Encoding detectionEditor testing· Conversion set

X12 EDI 214: SAMPLE

Short ANSI X12 214 SAMPLE transaction for EDI parser / translator tests.

File: EDI · Hl7 Edi
Use case: Encoding detectionEditor testing· Conversion set

X12 EDI 810 Invoice

An ANSI X12 810 invoice that references the 850 purchase order: ISA/GS/ST envelope with BIG, IT1 line items, and a total. The invoice twin of the purchase order, for testing EDI document flows.

File: EDI · Edi
Use case: Data importConversion testing· Conversion set

X12 EDI 850 Purchase Order

An ANSI X12 850 purchase order: ISA/GS/ST envelope with BEG, N1, and PO1 line items. A fixture for testing EDI parsers and translators. Paired with the 810 invoice for the same order.

File: EDI · Edi
Use case: Data importConversion testing· Conversion set

X12 EDI 855: SAMPLE

Short ANSI X12 855 SAMPLE transaction for EDI parser / translator tests.

File: EDI · Hl7 Edi
Use case: Encoding detectionEditor testing· Conversion set

X12 EDI 856: SAMPLE

Short ANSI X12 856 SAMPLE transaction for EDI parser / translator tests.

File: EDI · Hl7 Edi
Use case: Encoding detectionEditor testing· Conversion set

X12 EDI 940: SAMPLE

Short ANSI X12 940 SAMPLE transaction for EDI parser / translator tests.

File: EDI · Hl7 Edi
Use case: Encoding detectionEditor testing· Conversion set

X12 EDI 997: SAMPLE

Short ANSI X12 997 SAMPLE transaction for EDI parser / translator tests.

File: EDI · Hl7 Edi
Use case: Encoding detectionEditor testing· Conversion set

X3D: Interchange Cube

A 10 mm cube as X3D: the XML successor to VRML for web and interchange 3D. For testing X3D parsers and VRML↔X3D conversion.

File: X3D · Mesh
Use case: Conversion testing· Conversion set

XLIFF 1.2 (en → es)

An OASIS XLIFF 1.2 file with English source and Spanish target trans-units and notes: the classic interchange format between authoring tools and translation-management systems.

File: XLF · Xliff
Use case: Localization catalogsInternationalization+1· Conversion set

XLIFF 1.2: Inline codes (en to de)

The XLIFF 1.2 half of a version twin covering how each version represents inline markup and placeholders. XLIFF 1.2 keeps the original markup inline in <bpt>/<ept> and uses <g>, <x/> and <ph>; XLIFF 2.0 replaced all of them with <pc>, <ph/>, <sc/>/<ec/> and moved the markup into an <originalData> block referenced by id.

File: XLF · Xliff
Use case: InternationalizationLocalization catalogs· Paired fixture

XLIFF 1.2: Plurals (en to pl)

The XLIFF 1.2 half of a version twin covering how each version expresses a plural group. XLIFF 1.2 uses a <group restype="x-gettext-plurals"> whose trans-units are ordered by gettext form index; XLIFF 2.0 dropped restype, so the same content becomes one <unit> per CLDR category, named by category rather than by index.

File: XLF · Xliff
Use case: InternationalizationLocalization catalogs· Paired fixture

XLIFF 1.2: Translation state (en to es)

The XLIFF 1.2 half of a version twin covering how each version records translation progress. XLIFF 1.2 has approved="yes|no" plus a ten-value target state; XLIFF 2.0 removed approved and cut the vocabulary to four ordered values (initial, translated, reviewed, final) with everything else pushed into a namespaced subState.

File: XLF · Xliff
Use case: InternationalizationLocalization catalogs· Paired fixture

XLIFF 2.0 (en → es)

An OASIS XLIFF 2.0 file with the same content as its 1.2 twin, using the modern unit/segment structure, for testing XLIFF 2.0 parsers and 1.2-to-2.0 converters.

File: XLIFF · Xliff
Use case: Localization catalogsInternationalization+1· Conversion set

XLIFF 2.0: Inline codes (en to de)

The XLIFF 2.0 half of a version twin covering how each version represents inline markup and placeholders. XLIFF 1.2 keeps the original markup inline in <bpt>/<ept> and uses <g>, <x/> and <ph>; XLIFF 2.0 replaced all of them with <pc>, <ph/>, <sc/>/<ec/> and moved the markup into an <originalData> block referenced by id.

File: XLIFF · Xliff
Use case: InternationalizationLocalization catalogs· Paired fixture