You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Allow rasuvaeff/understudy^0.7. Widened rather than raised.
The #[Before] guard is checked through real PHPUnit. It was covered only
by a unit test calling runGuard() directly, which proves the condition and
nothing about what a user sees — the guard fires from #[Before], so the
failure lands on the BLAMELESS class, the one that ran after the leak, and
that attribution is the whole diagnostic. A fixture now leaks a context from
a class without the trait and pins the report, the attribution and the exit
code.
The Pest recipe runs in CI, and it was broken. The test that executes it
skips itself unless the fixture project is installed, which was every run of
every job — so the recipe had never actually been checked, and the fixture
still stubbed find(7) with when() and claimed the same call with expect(): two registrations of one call, which the engine has refused with ConflictingExpectation since 0.3. The README's Pest section has been right
all along; the fixture that was supposed to prove it had drifted, in the
third place this same mistake has now been found. The job has a checkout of
its own because the fixture's path repositories are written for the monorepo
layout — this package and the engine side by side — which is deliberate:
the recipe runs against the working tree of both.
infection/infection moves to ^0.35, matching the monorepo templates.
Re-measured: 12 of 12 mutants killed, unchanged.
AGENTS.md said the unit tests avoid PHPUnit's assertion counter; they use
it, by its new name. What actually guards the rename is the PHPUnit ^11.5
matrix job, and the note says so now.