Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

WebdriverIO Version

8.39.0

Node.js Version

20.16.0

Mode

WDIO Testrunner

Which capabilities are you using?

No response

What happened?

I have timeout defined for tests in the it hook (spec) which is greater than jasmineOpts.defaultTimeoutInterval specified in the wdio configuration. But during the execution, the timeout defined for the spec is neglected and a Timeout error is thrown as soon as the defaultTimeoutInterval is complete.

While debugging I found that the executeAsync method defined in the node_modules/@wdio/utils/build/shim.js file is trying to set the timeout and it is neglecting the custom timeout defined in spec and setting it to defaultTimeoutInterval as the this?.runnable?._timeout is always shown as undefined from below code when this method is called.

const _timeout = (this?.runnable?._timeout || globalThis.jasmine?.DEFAULT_TIMEOUT_INTERVAL || timeout) - TIME_BUFFER;

Note: I am using jasmine framework with WDIO.

What is your expected behavior?

The test should continue the execution for the time defined in the spec and should pass.

How to reproduce the bug.

1. Set the jasmineOpts.defaultTimeoutInterval to 10 seconds in wdio.conf.ts file.
2. Create a simple .ts file with a timeout of 15 seconds with below code:

describe('Debug Suite', () => {
it('Debugging Test', async () => {
console.log('Wait for 12 seconds');
await new Promise(r => setTimeout(r, 12000));
console.log('12 secs wait is complete');
}, 15000);
});

3. Run the test.

Relevant log output

[chrome 127.0.6533.89 windows #0-0] Running: chrome (v127.0.6533.89) on windows
[chrome 127.0.6533.89 windows #0-0] Session ID: a27b6029777683101c340acb2b093af3
[chrome 127.0.6533.89 windows #0-0]
[chrome 127.0.6533.89 windows #0-0] » file:///C:/Automation/sirenum/e2e-tests/specs/debug.spec.ts
[chrome 127.0.6533.89 windows #0-0] Debug Suite
[chrome 127.0.6533.89 windows #0-0]    ✖ Debugging Test
[chrome 127.0.6533.89 windows #0-0]
[chrome 127.0.6533.89 windows #0-0] 1 failing (10.1s)
[chrome 127.0.6533.89 windows #0-0]
[chrome 127.0.6533.89 windows #0-0] 1) Debug Suite Debugging Test
[chrome 127.0.6533.89 windows #0-0] Error: Timeout
[chrome 127.0.6533.89 windows #0-0]     at listOnTimeout (node:internal/timers:581:17)
[chrome 127.0.6533.89 windows #0-0]     at processTimers (node:internal/timers:519:7)

Spec Files:      0 passed, 1 failed, 1 total (100% completed) in 00:00:14

Code of Conduct

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

Is there an existing issue for this?

• I have searched the existing issues