nick8325 / nick8325/quickcheck
Events for Test Frameworks
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 790
- Forks
- 130
- Avg merge
- 16h 41m
- Merged PRs (30d)
- 2
Description
Many test frameworks wrap quickcheck, but quickcheck results are reported with Terminal Strings that are then parsed. For example https://github.com/UnkindPartition/tasty/blob/dcbf32078133aa2b569774c417cc49a49f5c573b/quickcheck/Test/Tasty/QuickCheck.hs#L267
It would be much easier to interface with an Event ADT.
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 reading the linked tasty file, quickcheck/Test/Tasty/QuickCheck.hs at line 267, to understand how Terminal Strings are produced and parsed around QuickCheck results. Determine the event representation and integration scope for test frameworks; done should provide a documented Event ADT interface that avoids parsing terminal output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100