Coder, Author, & Speaker. PHP 8.1 & 8.2 RM. ramsey/uuid. Open Source. Staff+ Engineer. he/him Co-admin of https:// phpc.social All original content © me & licensed CC BY-SA 4.0, unless otherwise specified. :cc: :ccby: :ccsa: The opinions expressed on this profile are my own and do not necessarily reflect the views of my employer or any affiliated organizations. Any information shared is intended solely for informational purposes and should not be construed as professional advice.
Coder, Author, & Speaker. PHP 8.1 & 8.2 RM. ramsey/uuid. Open Source. Staff+ Engineer. he/him Co-admin of https:// phpc.social All original content © me & licensed CC BY-SA 4.0, unless otherwise specified. :cc: :ccby: :ccsa: The opinions expressed on this profile are my own and do not necessarily reflect the views of my employer or any affiliated organizations. Any information shared is intended solely for informational purposes and should not be construed as professional advice.
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.
