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
As recently as php-code-coverage 9.2.11, the builtin match function reported coverage for each matching case. In 9.2.13, the cases are not even marked as coverable. Is this expected behavior? It seems quite useful to me to know which match cases are covered by tests.
Here is an example class:
<?phpdeclare(strict_types=1);
namespaceSmr;
class Bla {
publicint$foo;
publicfunction__construct(string$bar) {
$this->foo = match ($bar) {
'a' => 1,
'b' => 2,
'c' => 3,
// Some commentsdefault => 4,
};
}
}
Here is the coverage report from 9.2.11:
(Note that the tests covering cases 'a', 'b', and default are test_a, test_b, and test_default respectively, as expected.)
And here is the coverage report from 9.2.13:
Thanks for your time!
The text was updated successfully, but these errors were encountered:
As recently as php-code-coverage 9.2.11, the builtin
match
function reported coverage for each matching case. In 9.2.13, the cases are not even marked as coverable. Is this expected behavior? It seems quite useful to me to know whichmatch
cases are covered by tests.Here is an example class:
And here is the corresponding test:
Here is the coverage report from 9.2.11:
(Note that the tests covering cases
'a'
,'b'
, anddefault
aretest_a
,test_b
, andtest_default
respectively, as expected.)And here is the coverage report from 9.2.13:
Thanks for your time!
The text was updated successfully, but these errors were encountered: