rtfeldman / rtfeldman/node-test-runner
Allow running just non-fuzzed tests
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 83
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 5
Description
I have a suite of fuzzed and non-fuzzed tests. Sometimes I'd like to be able to run just the non-fuzzed tests, since they're much much faster (and the fuzzing floods the terminal with tons of noisy failures, see: https://github.com/rtfeldman/node-test-runner/issues/327)
A simple way to do this would be to allow elm-test --fuzz 0. Right now it says:
error: option '--fuzz <int>' argument '0' is invalid. Expected at least 1.
If this is implemented, there should be a conspicuous notice that all fuzz tests are skipped.
Another option would be calling the CLI arg --skip-fuzz
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 at the elm-test CLI entry point and inspect how the --fuzz argument is parsed and applied to test selection. Done means users can run only non-fuzzed tests and receive a conspicuous notice that fuzz tests were skipped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100