The operating manual for test parity.

A documentation-first release gate for teams that need every application file to have an obvious test, ownership declaration, and matched coverage threshold.

Read in orderInstallConfigureMeasureEnforce

StartRun the 5-minute setupCreate parity.yaml, generate coverage, run the first check.ConfigureModel your repositoryMap folders, suffixes, namespaces, exceptions, and minimums.UnderstandRead matched coverageSee when coverage came from the belonging test versus incidental execution.EnforceWire the gate into CIUse exit codes and JSON output to block weak test architecture.

Built for handoff.

Every failure names the source file, expected test file, rule, actual value, and threshold. A DevOps engineer can wire it into CI without knowing the application domain.

Chapter 01

Installation paths

Composer for PHP projects, PHAR for portable CI, and local binary usage for sample applications.

Open installation

Chapter 02

Repository model

Structure blocks describe source folders, test folders, file suffixes, explicit maps, and namespace behavior.

Open configuration

Chapter 03

Coverage semantics

Documentation distinguishes global coverage, minimum file coverage, and matched coverage from the belonging test.

Open coverage

Handoff package

What a DevOps engineer needs before deployment.

Entry pointphp vendor/bin/parity check --format=json
Required artifactParity JSON, PHPUnit XML, Clover XML, or Cobertura XML coverage report.
Config fileparity.yaml committed at the repository root.
Failure behaviorNon-zero exit when required rules fail.