Replies: 1 comment
-
|
I think WebdriverIO can do a better job to ensure that all workers are cleaned up / killed when ending the test run. The launcher process knows about all workers launched. If you are interested in making a contribution I recommend to take a look into |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
my test suite currently is running on very slow environment and i experience many timeouts. this allowed me to notice, that when Scenarios are run the worker process in between is not cleaned. the loops that are started in test case that timed out continue in the next test case polluting the results. any advice for cleanup to avoid this issue?
More details:
Serenity-js + cucumber+wdio
Scenario1 is polling for results (api call in a simple for loop) and times out
Scenario 2 logs the polling results with new scenario data
Beta Was this translation helpful? Give feedback.
All reactions