-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
“Pending” test case Tag #839
Comments
jnd-au
added a commit
to jnd-au/munit
that referenced
this issue
Oct 3, 2024
jnd-au
added a commit
to jnd-au/munit
that referenced
this issue
Oct 3, 2024
Show elapsed time for JS/Native Ignored tests (may be non-zero), to be consistent with JVM
jnd-au
added a commit
to jnd-au/munit
that referenced
this issue
Oct 3, 2024
- Also show elapsed time for JS/Native Ignored tests (may be non-zero), to be consistent with JVM
jnd-au
added a commit
to jnd-au/munit
that referenced
this issue
Oct 3, 2024
- Also show elapsed time for JS/Native Ignored tests (may be non-zero), to be consistent with JVM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It’s useful to support a “Pending” Tag annotation for new/incomplete test cases (especially if a user-supplied ticket tracker ID can be reported in test results). This kind of feature is supported by other frameworks like ScalaTest and Specs2. In terms of JUnit / framework reporting, Pending cases are usually logged the same as the Ignored tag. However, useful advantages of “Pending”, different from “Ignored”:
Without pending:
With pending:
The text was updated successfully, but these errors were encountered: