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
Expected behavior: When an unhandled error occurs during the execution of a test, it is reported (in the JUnit-style XML reports under target/test-reports/) as an <error>. Although I couldn’t find an authoritative definition or explanation of the XML schema, the following sources all agree that <error> is the correct element in this case:
Expected behavior: When an unhandled error occurs during the execution of a test, it is reported (in the JUnit-style XML reports under
target/test-reports/
) as an<error>
. Although I couldn’t find an authoritative definition or explanation of the XML schema, the following sources all agree that<error>
is the correct element in this case:In addition, reports produced by ScalaCheck also have an
<error>
.Observed behavior: The XML report produced by MUnit has a
<failure>
which is supposed to be for tests that fail an assertion or a check.Steps to reproduce: In shardulc/munit-scalacheck-error-repro.
The text was updated successfully, but these errors were encountered: