-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
JUnit XML logger does not handle TestSuiteSkipped event #5354
Copy link
Copy link
Closed
Labels
feature/loggingIssues related to logging test resultsIssues related to logging test resultsfeature/logging/junitIssues related to logging test results in JUnit XML formatIssues related to logging test results in JUnit XML formattype/bugSomething is brokenSomething is brokenversion/10Something affects PHPUnit 10Something affects PHPUnit 10version/11Something affects PHPUnit 11Something affects PHPUnit 11version/12Something affects PHPUnit 12Something affects PHPUnit 12version/13Something affects PHPUnit 13Something affects PHPUnit 13
Metadata
Metadata
Assignees
Labels
feature/loggingIssues related to logging test resultsIssues related to logging test resultsfeature/logging/junitIssues related to logging test results in JUnit XML formatIssues related to logging test results in JUnit XML formattype/bugSomething is brokenSomething is brokenversion/10Something affects PHPUnit 10Something affects PHPUnit 10version/11Something affects PHPUnit 11Something affects PHPUnit 11version/12Something affects PHPUnit 12Something affects PHPUnit 12version/13Something affects PHPUnit 13Something affects PHPUnit 13
Summary
Mandatory JUnit-Report attribute
testsin the first testsuite-Node is missing, ifsetUpBeforeClassuses e.g.self::markTestSkipped(). This is working fine with PHPUnit 9. As you can see in the examples, PHPUnit 9 handled the case also differently in the specific testsuite of the file containing the method call.We are skipping the test class using
setUpBeforeClassinstead of using thesetUpmethod, because there is a dataprovider generating many test cases that should not even be generated if skipped.I've just changed our tests and just wanted to let you know what I've discovered.
Current behavior
How to reproduce
Use a simple test with the
self::markTestSkipped()method call, e.g.:Expected behavior