-
Notifications
You must be signed in to change notification settings - Fork 15
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
Codeception acceptance tests fail randomly #526
Comments
Yep, this is happening on Travis. |
This does still happen, and happens on Travis sometimes still as well. However, it currently isn't egregious enough that I'm going to tackle it before this release. We'll get to it eventually though. |
lucatume/wp-browser#65 might be a fix for this issue. It hasn't been causing us much headache on Travis recently though. |
I just enabled an xDebug breakpoint on this error to see what is causing it, and the username submitted was shown to be |
Applying a fix similar to in that issue did not seem to help. I tried filling the field twice instead, and that seems to have worked; so far I haven't experienced these random failures anymore. |
The first time it is filled, it sometimes isn't ready to receive the keystrokes yet, and may end up as `dmin` instead of `admin`. Filling it twice seems to avoid this, and prevent random test failures. See WordPoints/wordpoints#526
Calling this fixed, if we continue to see issues we can reopen. |
While doing local testing, I've found that the tests will fail randomly. This will often occur the first 1-2 times that a test is run, then after that it will work correctly. After a few minutes the whole thing often ensues all over again. The failures always happen at the step after the login step, and it turns out that it is the login step itself that is failing.
I haven't yet tried to debug why this is happening, and perhaps it is related to my local set-up and isn't a global issue (I can't remember for sure whether I've observed failures matching this pattern on Travis CI or not).
One really strange aspect of it is that when a failure like this occurs, the failing test usually takes 2-3 times as long to complete as when it would succeed/fail for another reason. It makes me wonder if we have a race condition, and it only manifests itself when the underlying site is loading too slowly, or something.
The text was updated successfully, but these errors were encountered: