Samples
Each public sample demonstrates the same Parity proof in a different ecosystem. The samples are split into individual repositories so each one can install the public Packagist package during CI and prove the release path without private tokens.
| Sample | Language/framework | Test runner | Coverage input | Repository |
|---|---|---|---|---|
| PHP | Plain PHP | Fixture coverage | Parity JSON | php-sample |
| Laravel | Laravel-style PHP | Fixture coverage | Parity JSON | laravel-sample |
| TypeScript | TypeScript utility | Fixture coverage | Parity JSON | typescript-sample |
| AdonisJS | AdonisJS-style TypeScript | Fixture coverage | Parity JSON | adonisjs-sample |
| Rust | Plain Rust | Fixture coverage | Parity JSON | rust-sample |
| Cargo | Cargo project | Cargo | Parity JSON | cargo-sample |
| PHPUnit | PHP | PHPUnit | Parity JSON | phpunit-sample |
| Pest | PHP | Pest | Parity JSON | pest-sample |
| Jest | JavaScript | Jest | Parity JSON | jest-sample |
| Mocha | JavaScript | Mocha + NYC | Parity JSON | mocha-sample |
| Vitest | TypeScript | Vitest | Parity JSON | vitest-sample |
The Proof
Every sample is built around the same coverage shape:
| Scope | Coverage |
|---|---|
| Project/global coverage | 80% |
| Weaker file, all tests | 70% |
| Weaker file, matching test only | 40% |
| Stronger file, all tests | 90% |
| Stronger file, matching test only | 90% |
This proves that healthy global coverage can hide thin direct tests. Parity exposes that gap with matched-coverage and coverage-attribution.
Attribution Format
The samples use parity-coverage.json, a language-neutral attribution file:
json
{
"version": 1,
"globalPercent": 80,
"files": [
{
"path": "src/formatCurrency.ts",
"coveragePercent": 70,
"totalExecutableLines": 10,
"lines": [
{
"line": 1,
"coveredBy": ["formatCurrency.test::coversPrimaryBehavior"]
}
]
}
]
}CI Contract
Each sample runs the public package:
bash
composer global require testparity/parity --prefer-dist --no-progress --no-interaction
parity check --format=jsonThat makes the samples useful as release proof, not just documentation examples.

