-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[Bug]: Reporter.onTestCaseResult not called for test.todo in Jest 27 #12184
Comments
This caused https://youtrack.jetbrains.com/issue/WEB-51467. A workaround will be added in WebStorm 2021.3.2: |
This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
This seems reasonable to fix. |
@SimenB I'd like to work on this.. |
Go for it 👍 |
@SimenB could you please help me here how will i be able to call onTestCaseResult event for test.todo , |
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Version
27.4.5
Steps to reproduce
Reporter.onTestCaseResult doesn't get called on test.todo.
Expected behavior
jest --reporters ./my-reporter.js
should print:Actual behavior
Actually,
jest --reporters ./my-reporter.js
prints:Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: