typelevel / typelevel/cats-parse
It's hard to run targeted tests
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 245
- Forks
- 51
- Avg merge
- 3h 20m
- Merged PRs (30d)
- 1
Description
Because ParserTest contains so many tests, making isolated changes and quickly testing with testOnly or testQuick is slower than you'd ideally want it to be.
Splitting up ParserTest would enable a tighter test loop. Are you OK with that?
Contributor guide
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 locating ParserTest and measuring the current testOnly or testQuick feedback loop. Split the tests into focused groups while preserving existing coverage, then verify that targeted test commands run faster and all ParserTest cases still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100