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 Sep 7, 2018. It is now read-only.
The documentation says "When an asynchronous test runs for more than timeout ms, the runner will abort it and emit a test:timeout event."
That implies test:timeout will not affect synchronous tests. However, when I extend the timeout property the test pauses for that length of time even if the test is synchronous. This is also the case when I use when.js promises that successfully resolve.
That's strange. I can't reproduce this weird behaviour, neither with buster 0.7.11 nor with 0.7.13. Can you please reinstall buster and try again? Do you use a local or global installation of buster and on which OS? What does your buster.js file look like and how do you run your tests?
I'm using both a global and local install of buster on WIndows 7. I uninstalled and reinstalled it both globally and locally and that has seemed to fix the problem, so something must have gone wrong with my files.
The documentation says "When an asynchronous test runs for more than timeout ms, the runner will abort it and emit a test:timeout event."
That implies test:timeout will not affect synchronous tests. However, when I extend the timeout property the test pauses for that length of time even if the test is synchronous. This is also the case when I use when.js promises that successfully resolve.
When I run "always true" or "using promises" either individually or together, the tester will pause for ten seconds.
This is with Buster 0.7.11.
The text was updated successfully, but these errors were encountered: