Extend ALOpsAppTest to rerun failing tests
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 63
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
It might happen that failing tests do run when you manually trigger them. It is then hard to find the cause of the failure(s). This surely is the case with a number of MS tests. It does made sense to mark these test as a succes and it showed often that a rerun of only these failing tests did indeed mark them is succesful
Describe the solution you'd like
After having run all tests in the ALOpsAppTest I would like the ALOpsAppTest step to have an extra iteration (test run) of all failing tests before it is concluded.
Additional context
Freddy made some notes in this blog post on this feature.
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 with the ALOpsAppTest step and review how its initial test run identifies failing tests. Use the linked blog post for context, then add and verify an extra run for those failures before the step concludes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100