$this->assertStringContainsString('Runs the test script as defined in composer.json.', $output, 'The default description for the test script should be printed');
$this->assertStringContainsString('Run the codestyle fixer', $output, 'The custom description for the fix-cs script should be printed');
If you feel like helping, PRs are very much welcome, I don't think we absolutely need 100% coverage but having the most common use cases covered would already be very valuable. Please target the main branch if you want to contribute some, and feel free to announce it here if you start some larger chunk of work to avoid duplicating efforts.
The text was updated successfully, but these errors were encountered:
@theoboldalex great, thanks! Maybe wait until I get a chance to review the first one to make sure you don't run off and do more of them with the wrong assumptions. I'll try to get to it soon.
Also note the listing above is a bit outdated as I tried to work on this here and there when touching commands the last few months. But there is still plenty to be done :)
As you can see on this image, Command classes have very poor coverage currently (16% of lines covered in total):
Here some examples of how to write sane integration tests for most commands:
composer/tests/Composer/Test/Command/RunScriptCommandTest.php
Lines 92 to 113 in 176d258
composer/tests/Composer/Test/Command/ConfigCommandTest.php
Lines 23 to 52 in 176d258
composer/tests/Composer/Test/Command/BumpCommandTest.php
Lines 28 to 47 in 70f2dd6
If you feel like helping, PRs are very much welcome, I don't think we absolutely need 100% coverage but having the most common use cases covered would already be very valuable. Please target the
mainbranch if you want to contribute some, and feel free to announce it here if you start some larger chunk of work to avoid duplicating efforts.The text was updated successfully, but these errors were encountered: