Ben Ramsey1d ago

Is running a PHPUnit coverage report with `--strict-coverage` worth it? I’ve been doing this on a personal project, and every time I make some foundational change within Symfony (like something to do with the DI container or kernel, I have to update every single one of my test classes so it knows it’s okay to use the new class.

Maybe there’s a better way? I’ve only just begun doing this recently, so I’m new to it.

#PHP #PHPUnit

Show threadMarco "Ocramius" Pivetta1d ago
@ramsey I only do such coverage restrictions with very strict unit tests, zero integration tests: for those, `#[CoversNothing]`
Show threadBen Ramsey
@ocramius I guess that’s my problem. These are all on controller/command integration tests.
Mar 24 at 1:31amWeb
Show threadMarco "Ocramius" Pivetta1d ago

@ramsey yeah, the point of such strictness is to keep the size of the system under test under strict control.

I find such restrictions valuable for mutation testing, which becomes extremely expensive as your SUT grows too far.