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
Currently, when an assertion fails the exception message only includes the expectation, but not the actual events.
For example, the following assertion inspired by the JUnit 5 codebase fails with AssertionError: No JFR event of type <org.junit.EngineDiscovery> with attributes <{uniqueId=[engine:does-not-exist]}>:
Currently, when an assertion fails the exception message only includes the expectation, but not the actual events.
For example, the following assertion inspired by the JUnit 5 codebase fails with
AssertionError: No JFR event of type <org.junit.EngineDiscovery> with attributes <{uniqueId=[engine:does-not-exist]}>
:To find out what went wrong, I then had to add
println
statements to the test code, e.g.It would be great if the assertion message would include a (possibly shortened) list of actual events of the event type in question.
The text was updated successfully, but these errors were encountered: