Dashboard for Testing Metrics
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 144
Description
CI time is very important for the developer loop, slowdowns to CI can drastically reduce the dev loop. CI tracks information such as how long each test took to run. We can look into creating dashboards with this information, similar to the performance dashboards, which can track test times over time and flag tests that take exceedingly long (such as over 1 minute for CI).
Contributor guide
Research direction
Start by reviewing the existing performance dashboards referenced in the issue and how CI records test durations. Determine how timing data could be tracked over time and how tests exceeding one minute would be flagged. Done means a defined dashboard that exposes these trends and identifies tests over the stated threshold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ci-cd, developer-experience, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100