-
-
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
Streaming individual test results #6225
Comments
Now that I've gotten a primer on jest-circus, I guess this can be closed. It'll work out of the box (as long as one does not have an #4471 is pretty much the same thing anyways, so closing. |
@SimenB those are still two different reporting mechanisms:
|
Would it be possible to emit events from jest-circus outside of the vm as well? |
yes, but it'll introduce the whole world of parallelism, since we'll be running a lot of tests in parallel, the events will need to be handled differently :) |
Good point. Namespacing in test file name or something (maybe combined with runner?) might be enough? |
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. |
🚀 Feature Proposal
Right now we collect test results from a whole suite before passing it to a
testResultsProcessor
(and printing it). I'd like to also be able to know as each individual test completes without waiting for the whole suite.Motivation
2 use cases comes to mind:
As a bonus to the last point, we might want to stream multiple states per test -
pending
,running
andcomplete
or something might make sense.Example
Not really sure how it would be used. I guess an extra method in the reporter? Might make sense as part of Jest Hooks? https://github.com/facebook/jest/blob/master/packages/jest-cli/src/jest_hooks.js
Pitch
The UI for it does not have to live within Jest, but we should power custom reporters and test result processors to display real time data about a test suite
The text was updated successfully, but these errors were encountered: