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
{{ message }}
Repository navigation
Allure not showing Junit5 ignored test(these are ignored as before all method failed) #420
If before all the fails the subsequent test is ignored. Allure fails to capture these ignored cases and only shows the main class name as failed in reports.
What is the expected behavior?
The ignored test should be included either as failed or ignore.
What is the motivation / use case for changing the behavior?
Due to this the count of the number of tests executed by in allure is inconsistent. causing confusion.
E.g one run we have 120 cases and other we have only 100 are 20 were not captured as before all for a set of the test failed
Closing as not planned. When @BeforeAll fails, JUnit Platform does not emit execution events for the tests inside the failed container, so the adapter cannot produce accurate skipped or failed results for them—especially for parameterized and dynamic tests whose invocations do not exist yet. Creating synthetic results would distort counts and retry/history identities. Since #1391, Allure reports the @BeforeAll failure as a run-level error with the original exception and states that the tests inside did not run.
Activity
baev commentedon Sep 3, 2026
Closing as not planned. When @BeforeAll fails, JUnit Platform does not emit execution events for the tests inside the failed container, so the adapter cannot produce accurate skipped or failed results for them—especially for parameterized and dynamic tests whose invocations do not exist yet. Creating synthetic results would distort counts and retry/history identities. Since #1391, Allure reports the @BeforeAll failure as a run-level error with the original exception and states that the tests inside did not run.