Shrinking

Open
#103 6 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
testing

Research direction

The issue proposes adding shrinking but names no files, tests, or entry points. Start by reading the QuickCheck implementation and comparing how shrinking works in other language implementations; define the intended behavior and tests before estimating the change. Done means shrinking is implemented and its behavior is covered by tests.

Written by the indexing model from the issue text.

Description

type: enhancement

New to QuickCheck on the whole, but I understand shrinking is a popular feature in other language implementations. Would be cool to see it here 🙂

Dominant language
PureScript
Stars
108
Forks
42
Avg merge
2d 23h
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from purescript/purescript-quickcheck

All issues in purescript/purescript-quickcheck

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.