Fuzz workflow resets
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 102
- Forks
- 29
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 22
Description
We should make sure workflow resets are done by the fuzzer/kitchen-sink workflow.
This will probably cause all manner of consternation and violate many different assumptions, but that's kinda the point. ;) Hopefully all the issues we find in doing so are merely test issues, but one never knows.
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 fuzzer/kitchen-sink workflow and trace how workflow resets are currently handled. Done means that workflow resets are exercised there and the resulting test failures or assumptions are identified for follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100