Copy a working sample before you write your own config.

Parity ships with runnable public examples across PHP, JavaScript, TypeScript, Rust, Laravel, Vite, and AdonisJS-style layouts. Each sample installs Parity from Packagist in CI and includes code, tests, coverage output, config, and expected result.

Browse sample repositories Configuration reference

PHPphpunitattributed XML

PHPpestcovers() ownership

JSjestParity JSON

JSmochaNYC + attribution

TSvitestVite project

Rustcargoportable coverage

Sample folders includecode/tests/coverageparity.yamlresult.md

Includedcode/

A minimal real application layout.

Includedparity.yaml

The exact configuration for that stack.

Includedresult.md

The expected Parity output to compare against.

SampleRunnerCoverageWhat it proves

phpunitPHPUnitPHPUnit XMLAttributed per-test coverage.

pestPestPHPUnit XMLcovers() ownership links.

jestJestParity JSONJavaScript structure plus matched coverage proof.

mochaMocha + NYCParity JSONNode coverage attribution compatibility.

vitestVitestParity JSONTypeScript/Vite layout mapping.

cargoRustParity JSONPortable non-PHP attribution example.

Sample anatomy

Every sample is a reproducible contract.

A sample is not a screenshot or fixture blob. It is a small application with tests, generated coverage, Parity config, and a checked-in result so regressions are obvious.

testparity/jest-samplecode/parity-coverage.jsonparity.yaml.github/workflows/parity.yml

Best when adoption depends on seeing your stack represented.

The lab style makes Parity feel practical and low-risk. It should be a strong secondary section even if another variant becomes the homepage.