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
That means that when I use waitUntil rather than waitUntil(timeout: 5), instead of using Nimble.AsyncDefaults.Timeout = 10, (executed in TestingAppDelegate init, checked with the debugger that is called before the test), 1 will be use as a default value, rather than 10.
Is that normal?
Apart from that (I am still researching this), several of my tests are failing after I moved from xcode 9.0 to 9.1, basically waitUntil fails saying "Waited more than 1.0 second". But if I use waitUntil(timeout: 2) then they work (I am using Mockingjay to simulate a network response).
The text was updated successfully, but these errors were encountered:
What did you do?
Tried to change the default wait timeout from 1 to 10 using
Nimble.AsyncDefaults.Timeout = 10
but waitUntil continues using 1
What did you expect to happen?
I expected that 10 was going to be used.
What actually happened instead?
It's still using 1.
Environment
List the software versions you're using:
Please also mention which package manager you used and its version. Delete the
other package managers in this list:
Project that demonstrates the issue
In the file DSL+Wait.swift I see:
That means that when I use waitUntil rather than waitUntil(timeout: 5), instead of using Nimble.AsyncDefaults.Timeout = 10, (executed in TestingAppDelegate init, checked with the debugger that is called before the test), 1 will be use as a default value, rather than 10.
Is that normal?
Apart from that (I am still researching this), several of my tests are failing after I moved from xcode 9.0 to 9.1, basically waitUntil fails saying "Waited more than 1.0 second". But if I use waitUntil(timeout: 2) then they work (I am using Mockingjay to simulate a network response).
The text was updated successfully, but these errors were encountered: