What's the correct way to test a Racket build?

[Yongming Shen]

Hi,

After an in-place build of Racket from source (from a git clone), what's the correct way to test that Racket functions correctly? I can't find documentation on this. Is it simply running "racket/bin/raco test pkgs/racket-test" from the root of the repository? Also, for a release (say, tag v7.6), it is normal for "racket/bin/raco test pkgs/racket-test" to report a few test failures?

Thanks,

Yongming

[Sam Tobin-Hochstadt]

The most basic test suite is run with `racket/bin/racket
pkgs/racket-test-core/tests/racket/test.rkt`.

There are a lot of other tests; a good guide is the CI suite here:
https://github.com/racket/racket/blob/master/.github/workflows/ci-push.yml#L283-L318

In general, and certainly for a release build, these tests should all
pass, although there's a possibility that a few might fail
intermittently due to test flakiness. If there's a consistent failure
not related to your changes, that's a bug.

Sam

> --
> You received this message because you are subscribed to the Google Groups "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to racket-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/465f8808-032e-4cc0-b13e-4618acfc1813%40googlegroups.com.