The committers listed above are authorized under a signed CLA.

• ✅ login: rashiq231 (dd8fff3, 682bf06, 9265924, 0fb03fc, 2abc730)
• ✅ login: christian-bromann / name: Christian Bromann (22e5460, 68c1c63, cab3808)

updated as per your comment. Could you please verify now?

@rashiq231 I think we need to update one more unit test:

 FAIL  packages/webdriverio/tests/utils/Timer.test.ts > timer > promise > should be rejected without promise
AssertionError: expected Error: timeout to match object Error: return value was never truthy
  - Expected  - 1
  + Received  + 1

    Error {
  -   message: 'return value was never truthy',
  +   message: 'timeout',
    }

okay... I will update the test case for Timer.
But, a little clarification, shouldn't we need to maintain the existing error message - 'return value was never truthy', when ever the function returns false instead of resolving to false?
Shouldn't the timeout error which we updated in the timer should occur when the given time is exhausted?

The docs implicitly say:

It expects a condition and waits until that condition is fulfilled with a truthy value to be returned.

So there is no reason to have an error message stating the obvious and use the timeout error because that is what happens at the end: the timer times out because no truthy value was returned.

Congratulations on your first WebdriverIO contribution! This project can't live without the participation of the community. We would love to see more from you, so let us know if we can help to find interesting areas for you to contribute to. Join our Discord channel and reach out to us. We appreciate you 🙏 ❤️

@christian-bromann , Thank you for your help and support :)