-
-
Notifications
You must be signed in to change notification settings - Fork 729
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
Issue with running multiple test scripts w/ WebDriverIO. Unhandled promise rejection #241
Comments
Do you use |
Yes, I have that option set in the codeceptjs config. |
Issue has been fixed in version 0.4.7 with the merging of PR #240. |
Hello, Got here by google and it seems the problem is back as i encountered it today. :) |
same here. I do not use the restart option (neither restart: false nor restart:true) nodejs: 4.4.1 config-file:
|
I am also getting |
Please, provide your test to reproduce the issue |
@APshenkin I'll link you to our tests. If I get some free time I might try to make a trimmed down reproducible case. codecept.conf.js Travis CI log with error and codeceptjs verbose: |
I only have this issue when the tests are running on Travis, not when running them locally. @thesupad @joelgrimberg Did either you figure out what the problem was? Do you run into this error when running the tests locally or only on a CI build system? |
I have the same issue with when i am using it with Browserstack: NPM - 3.10.10 |
Just reproduced it again |
Still face the same err "Error: A session id is required for this command but wasn't found in the response payload". Can someone guide me what the err actually means? |
When running all of my test scripts, the first Feature will pass, but the rest will receive the following error:
NPM - 3.10.3
codeceptjs - 0.4.6
node - 6.7.0
WebDriverIO - 4.2.16
This was previously working on
codeceptjs 0.4.5
, And works if I roll back tocodeceptjs 0.4.5
Running a single test script, (e.g.
codeceptjs run . --grep "@header"
) Works perfectly fine.Any thoughts?
The text was updated successfully, but these errors were encountered: