RQ

Racket QuickCheck

Free#27 of 27 in Property-Based Testing Tools

Racket QuickCheck: A focused, free property-testing library for Racket teams using RackUnit. Ranked #27 of 27 in Property-Based Testing Tools by our editors (6.7/10); pricing: Free plan; best for racket teams using RackUnit.

6.7/10★★★☆☆Editor score

View Racket package

At a glance

• Editor score
  6.7 / 10
• Pricing
  Free plan
• Best for
  Racket teams using RackUnit
• Free plan
  Yes
• Paid from
  Free
• Supported languages
  Racket
• Facts checked
  20 Sep 2026

• Where it wins

  • Generates random inputs with built-in and custom generators
  • Supports configurable test counts and test sizes
  • Reports counterexamples and integrates with RackUnit

• Where it doesn't

  • Supports Racket rather than multiple programming languages
  • Does not provide shrinking for failing cases
  • Its test-runner integration centers on RackUnit

Our verdict on Racket QuickCheck

Racket QuickCheck is a free property-based testing library for Racket programs. It is designed for developers who want to express expected behavior as properties, generate varied inputs, and run those checks inside a Racket development environment. Its strongest fit is a Racket team already using RackUnit, because property-checking forms connect generated tests with that test runner.

The core workflow covers both specification and test-data generation. Developers can define properties, use built-in arbitrary values and generators, or construct custom generators for domain-specific inputs. Test counts and test sizes are configurable, with the documented default set at 100 tests and supported counts including 1,000 and 10,000. When a property fails, Racket QuickCheck reports a counterexample, along with result and test-count information. This gives teams a direct way to inspect failing generated cases while keeping the test definition focused on behavior rather than individual examples.

Its main limitation is the absence of shrinking. A failing counterexample is reported, but the package does not provide the reduction step that can make a generated failure smaller and easier to diagnose. The package also stays narrowly focused on Racket and RackUnit, so it suits teams committed to that language and test runner rather than organizations seeking cross-language coverage or a broader test ecosystem. Choose Racket QuickCheck for free, configurable property testing within a Racket and RackUnit workflow; choose another tool if shrinking or wider platform support is central to the evaluation.

Your product? Our editors can test Racket QuickCheck in depth and publish a review, labelled as paid · from $149/mo →

Racket QuickCheck pricing

Racket QuickCheck fact sheet

Racket QuickCheck integrations

Racket QuickCheck lists 1 integrations on its own site.

• RackUnit

Alternatives to Racket QuickCheck

• fast-checkA deep, runner-agnostic testing library for JavaScript and TypeScript teams.9.4
• HypothesisA focused Python library for generated inputs, shrinking, and stateful tests.9.3
• ProptestA focused Rust framework for generated inputs, shrinking, replay, and stateful tests.9.1

See all Racket QuickCheck alternatives →

Used Racket QuickCheck? Be the first to review it

The editor score above is our own research. What this page doesn't have yet is a reader's view — what you used Racket QuickCheck for, what worked and what didn't. No stars are seeded and no review is paid for; an editor reads every one before it appears.

Write a reviewTwo minutes · verified accounts only · read by an editor before it appears

Website

Reviews come only from verified accounts. Sign in or create an account first — your e-mail is never shown.

Your rating

5 stars★4 stars★3 stars★2 stars★1 star★

Title

Your review

0 characters · at least 80, up to 3,000

Pros (optional · one per line)

Cons (optional · one per line)

Your name (shown with your review)

Role (optional)

Company (optional)

How long have you used it?Prefer not to sayLess than a month1–6 months6–12 months1–2 years2+ years

I've used Racket QuickCheck myself and this is my honest opinion — nobody paid or asked me to write it.

Send my reviewPosted from your verified account. Reviews appear after an editor reads them, usually within two working days.

Featured on iTechGuides

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated 7 Oct 2026 · How we research and update