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
PHPUnit has a --group option that allows to specify which group of tests should be run. While Paratest has the same option, it behaves differently: it does not filter out test classes that do not have the @group annotation. Taking as example the code below (one class per file), I would expect that only the second test class is executed using the command vendor/bin/paratest --group=group1 while instead both are:
Instead running plain PHPUnit using the command vendor/bin/phpunit --group=group1 works as expected. I tracked the error down to the SuiteLoader::testMatchGroupOptions method which returns true as long as no groups are defined on the test class. Even though I strongly believe that this is a bugfix, it also causes a huge BC. I'm willing to open PR to address the problem anyway, so let me know how we want to proceed
The text was updated successfully, but these errors were encountered:
PHPUnit has a
--group
option that allows to specify which group of tests should be run. While Paratest has the same option, it behaves differently: it does not filter out test classes that do not have the@group
annotation. Taking as example the code below (one class per file), I would expect that only the second test class is executed using the commandvendor/bin/paratest --group=group1
while instead both are:Instead running plain PHPUnit using the command
vendor/bin/phpunit --group=group1
works as expected. I tracked the error down to theSuiteLoader::testMatchGroupOptions
method which returnstrue
as long as no groups are defined on the test class. Even though I strongly believe that this is a bugfix, it also causes a huge BC. I'm willing to open PR to address the problem anyway, so let me know how we want to proceedThe text was updated successfully, but these errors were encountered: