[feature] --no-only, --no-skip CLI flags
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3k
- Forks
- 101
- PR merge metrics
- No merged PRs in 30d
Description
Currently, there's a risk of forgetting to remove .only and shipping a buggy program.
To prevent that, for example, tap has a CLI flag --no-only which disables .only functionality and it's guaranteed that all tests will be ran. I use that on CI.
Same way, we could disable skipping via --no-skip.
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 CLI argument parsing and the existing .only and skip handling; the issue names no files or tests, so first locate those entry points and their coverage. Done means supporting --no-only and --no-skip, with CI able to ensure all tests run and skipping is disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100