-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[🐛 Bug]: Mocha Step Definition Timeout #12714
Comments
new issue created as requested here: |
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! |
@talbss I think because the way wdio wraps mocha, setting this.timeout() inside of it() would not work. To set timeout for it(), try putting timeout after like this instead
|
Yes i know and i have already done this change on my tests. |
Have you read the Contributing Guidelines on issues?
WebdriverIO Version
8.36.0
Node.js Version
v20.12.1
Mode
Standalone Mode
Which capabilities are you using?
What happened?
mocha offers the possibility to overwrite the test timeouts https://mochajs.org/#timeouts
At suite level:
At test level
What is your expected behavior?
The mocha timeout (3000ms) defined in the wdio.conf.js file should be overwritten at suite level or test level:
At test level, the overwritten timeout is not taken into account, even if it is correctly overritten:
this code:
gives following output:
but timeouts after 5000ms
How to reproduce the bug.
clone https://github.com/talbss/wdio-v8
npm i
npx wdio
Relevant log output
Code of Conduct
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: