codeforequity-at / codeforequity-at/botium-cli
Botium cli is timing out even with the timeout set to 30000ms
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Botium cli is recently timing out even with the timeout set to 30000ms. Here is a sample error from our test. Can you please check?
Error: thrown: "Exceeded timeout of 30000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
Thanks,
Ram
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported Botium CLI failure using the sample Jest timeout error and inspect how the CLI's tests configure their timeout. Confirm the cause of the 30000ms timeout being exceeded, then verify that the intended timeout is honored by the relevant test run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100