-
Notifications
You must be signed in to change notification settings - Fork 7.3k
many tests are too slow #4932
Comments
These tests all take 1s or longer:
Those would be a good place to start. |
How do I run a test for a single file individually? Eg. I want to just run the tests in |
You can run either |
Awesome. Thank you :) |
Is this still a wanted change? I'd be willing to work on this |
I think this can be closed. Slow tests have been moved to test/pummel and io.js goes a step further by running most tests in parallel as of nodejs/node#172. |
Marking this as a potential iojs-backport, but closing. Can reopen if we feel this is still something worth pursuing in this stream. |
There are a lot of tests that are too slow. Some of them do 1000ms timeouts and stuff, but are perfectly fine to run much faster than that, especially when they should be responding to events rather than waiting on a setTimeout. A full second is way too long for anything in test/simple/, since we run that very frequently.
It'd be great to have most tests run in under 50ms, or perhaps as much as 200ms for cases where timing is actually relevant to the test.
I'd suggest that some tests should just be retired, but every time I think that, some ancient test ends up catching a regression, so they should probably all stay.
The text was updated successfully, but these errors were encountered: