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
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
I've noticed that, for longer tests, the output will sit and you won't know what is causing a hang up or not. It'd be nice if this reporter logged each test success/failure in the suite as it happened, rather than after the entire test suite is run.
The text was updated successfully, but these errors were encountered:
This is great - very clear what is passing or failing.
However, this output only appears after the entire test spec has run. We have a test spec that runs several dozen it statements (basically testing a bunch of different pages for a generic error). In that case, you get zero output until every single test has wrapped up.
What I'd like is for the above output to appear as these individual tests succeed / fail. i.e., in the above example, I'd like to see [chrome #0-0] ✓ Checking for existing components as soon as that individual test is complete, rather than waiting for the whole spec.
This is a feature request.
I've noticed that, for longer tests, the output will sit and you won't know what is causing a hang up or not. It'd be nice if this reporter logged each test success/failure in the suite as it happened, rather than after the entire test suite is run.
The text was updated successfully, but these errors were encountered: