Re-enable coverage tracking for src/Command/*
#469
Labels
bug
Inconsistencies or issues which will cause a problem for users or implementors.
src/Command/*
#469
In the tests, Composer commands are run in the same process as the tests to allow for easy debugging and coverage reporting. That functionality is implemented here: https://github.com/cweagans/composer-patches/blob/main/tests/_support/Helper/Composer.php
However, it does not work at all for the custom commands that are included in this plugin. There is a test that covers
composer patches-relock
andcomposer patches-repatch
(https://github.com/cweagans/composer-patches/blob/main/tests/acceptance/CommandsCept.php), but if I change the->runShellCommand()
lines to their corresponding->runComposerCommand()
calls, I get all kinds of very strange errors.I'm confident that those two commands are well tested and testing
patches-doctor
thoroughly isn't going to be a very straightforward thing. I'm not interested in holding up the 2.0.0 release on fixing that particular issue, but I also don't want to artificially deflate the amount of test coverage that this plugin has. Therefore, I've ignored the entiresrc/Command
directory for coverage tracking.DoctorCommand
isn't well tested right now, but I'll accept that.The text was updated successfully, but these errors were encountered: