[💡 Feature]: Timeout for Entirety of WebDriverIO Test Runner Instance

[samuelfreiberg]

Is your feature request related to a problem?

Imagine a scenario where the WebDriverIO test runner is running underneath a different test harness, and that parent test harness has a timeout.

We have a native environment that runs automation in a CI loop. I've developed an integration layer that allows us to run WebDriverIO test harness underneath our native test harness. (Why? So we have the ability to run JS test code in our native environment, which we haven't been able to do. This helps us with our goal of writing JS features moving forward).

If the parent test harness reaches its default timeout, it immediately stops execution of the test instance. Therefore, we don't get any debugging information from WebDriverIO because it was deleted before logs can be made.

This would be an issue for all situations where WebDriverIO is running underneath a process that has a timeout. It doesn't have to be a different test harness, it could simply be a CI loop that has a timeout.

Describe the solution you'd like.

We would like the ability to set a timeout on the WebDriverIO instance so we could fail early (if necessary) and still output all the logs.

For example, in the WebDriverIO configuration file, something like:

testRunnerTimeout: 50000 // 5 minutes from start to end

So the second WebDriverIO starts execution, it has 5 minutes to finish. If it doesn't, export all logs and fail.

Describe alternatives you've considered.

No response

Additional context

We're a huge consumer of WebDriverIO and we're integrating it at a high-capacity. It would be great if we could work together to do this! Thanks.

Code of Conduct

• I agree to follow this project's Code of Conduct

[christian-bromann]

testRunnerTimeout: 50000 // 5 minutes from start to end

I would just call it timeout and have it being part of the WebdriverIO.Config type.

[wdio-bot]

Thanks for reporting!

We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!