Choosing a Unit Testing Framework for Small Racket Educational Projects

Problem

When building a small educational tool in Racket (under 100 KB), you need a testing approach that adds virtually no external dependencies, works in the REPL, and is easy for students to grasp.

Decision and Constraints

The decision is: use rackunit for straightforward unit tests, quickcheck for property‑based tests, and plai for beginner‑friendly examples. Constraints are:

• Project size < 100 KB
• Target audience: students
• Minimal external dependencies
• Easy integration with the Racket REPL

Framework Comparison

Framework	Type	Best For	Complexity	Dependency
rackunit	Unit testing	Simple assertions & standard logic	Low	Built‑in
quickcheck	Property‑based	Complex logic & edge‑case discovery	Medium	External library
plai	Educational wrapper	Beginner‑friendly syntax	Low‑Medium	Built‑in (teaching language)

Trade‑offs

rackunit offers zero‑overhead and immediate REPL feedback, but you must write each test case manually, which can miss edge cases.

quickcheck generates random inputs to test properties, increasing bug‑finding power, yet requires learning its syntax and adding a package dependency.

plai simplifies assertions for newcomers, but its test reporting is less configurable than rackunit’s.

Concrete Implementation: rackunit Factorial Test

For most small educational projects, rackunit is the simplest starting point. Below is a complete test suite for a factorial function.

#lang racket
#require rackunit

;; Function under test
(define (factorial n)
  (if (= n 0)
      1
      (* n (factorial (- n 1)))))

;; Test suite
(define factorial-tests
  (testsuite "Factorial Tests"
    (testcase "for 0" (check-equal? (factorial 0) 1))
    (testcase "for 1" (check-equal? (factorial 1) 1))
    (testcase "for 5" (check-equal? (factorial 5) 120))
    (testcase "for 10" (check-equal? (factorial 10) 3628800))))

;; Run the tests
(run-tests factorial-tests)

Verification

1. REPL method: Load the file in DrRacket or run racket -l yourfile.rkt; the call to run-tests prints All tests passed. when every assertion succeeds.
2. Command‑line method: Execute raco test yourfile.rkt. The tool discovers the test suite, runs it, and returns exit code 0 on success or a non‑zero code if any check fails.
3. To inspect details, redirect output: raco test yourfile.rkt > test-output.txt 2>&1 and verify each line contains check-equal? results.

Note: rackunit is part of the standard Racket distribution since version 6.0; the function names used above (check-equal?) are stable. If you work with a very old release (< 6.0), consult the release notes for any API differences.