I’m adding some test cases to the existing test files in racket-test-core. I’ve only used rackunit before though, which these tests don’t use. How does this test framework work?

Creatively

Here’s an example: https://github.com/racket/racket/blob/master/pkgs/racket-test-core/tests/racket/basic.rktl#L122

That means that (equal? ’a “a”) is supposed to produce #f

Then https://github.com/racket/racket/blob/master/pkgs/racket-test-core/tests/racket/basic.rktl#L143 is an exception test

The actual test harness is defined here: https://github.com/racket/racket/blob/master/pkgs/racket-test-core/tests/racket/testing.rktl and is older than all of my students

To run them: raco test -l tests/racket/test or run the same test.rkt file.

and fwiw some test files may also define their own wrapper over test, e.g. https://github.com/racket/racket/blob/master/pkgs/racket-test-core/tests/racket/control.rktl#L15

whispering quietly to myself one refactoring at a time, jack, one refactoring at a time

When (test expected f x y) checks that (f x y) produces expected, does it do so with eq? or with equal?

ah I see in the comments for testing.rktl that it uses equal?

Rewriting that isn’t likely — believe me I’ve thought about it

And to run them I recommend racket -f quiet.rktl basic.rktl or whatever file instead of basic you’re modifying

I uh, don’t actually build racket from source on my machine. I still have 7.8 installed. When I edit stuff in core racket I just rely on the pull request CI.