Automated notification when CI tests fail repeatedly in rolling builds
Open
- Dominant language
- C#
- Stars
- 109
- Forks
- 85
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 1
Description
It was suggested that we could use RunFo to determine when a particular test had enough failures that it should be reported.
This could be a pipeline run on a schedule. Need to determine how many days of rolling builds to take into account and what the threshold is for reporting.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by investigating how RunFo exposes repeated test failures across rolling builds and how a scheduled pipeline could consume that data. The open decisions are the rolling-build time window and reporting threshold; done means an agreed, scheduled notification reports tests that exceed the threshold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100