-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add ability to add up before() runtime with it() runtime #700
Comments
yeah there's been some discussion about this, it's a bit of a tough call, I dont want to bloat mocha with a bunch more options, I think we should just come to a conclusion on what's expected. I'm a bit torn between the two personally, we could also clutter the output a bunch more and add both but that's pretty ugly |
Well it depends on the testing pattern. Personaly mine is to have one assert per it, so I usually do some call in before() and then verify multiple expectations in multiple it()'s so I can see all failures at once. Of course then, timing that omits before is pretty much useless to me. |
im leaning towards it being additive and we leave it at that for now, at least then there's the indication of what is causing the entire suite to bog down |
cool |
dup of #419 |
--slow is highlighting only long running tests, measuring only time it() took to execute.
This leads to missed slow tests if slow part is hidden in test preparation (in before()).
It would be useful to have some option (--measure-before ?) to highlight tests that are above threshold together with appropriate before(Each)().
The text was updated successfully, but these errors were encountered: