valkyrjaio / valkyrja-php / 30323235461 / 1
100%
26.x: 100%

DEFAULT BRANCH: 26.x
Ran
Files 1138
Run time 29s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 100.0%. Remained the same
30323235461.1

push

github

web-flow 
[Documentation] Document parallel branch and path coverage in a PHPUnit README (#934)

# Description

Adds a `README.md` to `.github/ci/phpunit/` documenting the parallel
branch and
path coverage harness added in #933, which otherwise is only
discoverable by
reading the shell script.

Also includes the one-line `.gitignore` whitelist the README needs to be
tracked
at all, since that directory denies everything by default.

The README covers what the directory is, a table of the root `composer`
scripts
and which one is the enforced gate, then the sharding capability in
depth: why it
exists (the serial run takes ~32 minutes and exceeds Composer's default
process
timeout, so branch coverage was never actually looked at), how it works,
the
measured 190s vs 1942s result, the environment options, and how to drive
individual shards the way a CI matrix would.

It also records the two non-obvious behaviors a future reader would
otherwise
rediscover the hard way:

- **Merged totals differ slightly from a serial run** — an Xdebug
artifact around
`match` lines, which is why the enforced line gate stays on the serial
run.
- **Shards need isolated storage** — `TestCase::tearDown()` wipes shared
storage
  after every test, hence `VALKYRJA_TEST_STORAGE_PATH`.

And it states plainly that path coverage is a diagnostic rather than a
100%
target, so nobody sets out to chase a combinatorial number.

Every script name, environment variable, and build path named in the
README was
verified against the code, and both documented invocations
(`composer phpunit-path-coverage-shard Http` and `...-merge`) were run
to confirm
the argument pass-through works as written.

## Types of changes

- [ ] Improvement _(non-breaking change which improves code)_
- [ ] Bug fix _(non-breaking change which fixes an issue)_
- [ ] New feature _(non-breaking change which adds functionality)_
- [ ] Deprecation _(breaking change which removes functionality)_
- [ ] Breaking change _(fix or feature tha... (continued)

12591 of 12591 relevant lines covered (100.0%)

23.5 hits per line

Source Files on job 30323235461.1