-
Notifications
You must be signed in to change notification settings - Fork 201
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
Tests failed for reason of timeout. #80
Comments
You can increase the timeout if you like via frisby.globalSetup({
timeout: 10000
}); |
var frisby = require('./lib/frisby'); TRY THIS |
I'm already made earlier action in your first comment and it doesn't help me. Second - I did not check out yet. I'll try today. Thank you. |
Try putting |
Thank you guys!!! var frisby = require("frisby"), frisby.globalSetup({ In current time all tests run successfully) |
If I run a group of tests in separate files as such If I run each file in it's own session like so, all is well |
Yes unfortunately I have run into this as well. I am not sure the solution to this off hand - it's something I will have to look into (unless someone else can help!). |
I am also getting random 5000 timeouts even though I'm setting a global timeout in every file to 30000 |
@vlucas at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)
Finished in 8.695 seconds
3 tests, 10 assertions, 2 failure, 0 skipped I've set the globalSetup timeout to 30000 and if you notice, frisby tests got finished in 8.695 Earlier I did not have this issue in my other laptop (may be that was old version of frisby/nodejs) |
👍 |
Any movement on this? |
frisby.globalSetup({ worked for me. |
Worked for me |
Hello, help please to resolve problem. While my tests are running one by one in script some of them are failed for reason of timeout 5000ms. How can I fix this problem?
Thanks.
The text was updated successfully, but these errors were encountered: