files testing degradation tracking
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 104
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Attach everything. You know which files have signature hits from whenever a test was last run.
Only show the files that have a hit by default. Have a button to expand the rest.
If we want to really do this right. We should show existing DFI file hits as well as previous, but ghosted out.
If someone runs a test and sees a file they expect to fire, go grey (ghosted), they will see it and can adjust accordingly.
In a nut shell:
Save all files
Hide files which never had a signature hit
Ghost/grey files that used to have a signature hit but don't now
Show files that have active signatures
I think you worry about API only for this, if the UI is easy enough. Implement that too.
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 tracing how test results expose files with signature hits and how the UI currently presents those results; the issue names no files or tests. Done means all files are retained, never-hit files are hidden by default, former hits are ghosted, active hits remain visible, and the API and UI support the behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100