Retry failed tests automatically
- Dominant language
- Go
- Stars
- 2.7k
- Forks
- 280
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 2
Description
### 🤔 What's the problem you're trying to solve?
It is always frustrating when the test fails with no reason and just works fine with a retry. It is common to fail one or other test when there are thousands of tests running in parallel. There can be multiple reasons for failure like network slowness, overloaded server.
### ✨ What's your proposed solution?
It would be really helpful if we have a feature to rerun the failed tests.
Rerun option is also provided by other tools for example
ctest -> https://cmake.org/cmake/help/v3.17/manual/ctest.1.html ( --repeat until-pass:n )
maven-surefire-plugin -> https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html
I have also seen in here https://github.com/cucumber-rs/cucumber/issues/212
It would be really helpful, if you consider this. Thank you :)
### ⛏ Have you considered any alternatives or workarounds?
_No response_
### 📚 Any additional context?
_No response_
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the Go test execution or runner flow and its existing failure handling; define the retry configuration and verify that failed tests can be rerun and that the final result reports success or failure correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100