Jacqueline Firth
Jacqueline Firth
RackUnit doesn't handle everything, nor should it. It would be useful to have a few words in the docs about community packages related to RackUnit, such as: - Packages that...
It would be helpful to have a document describing what good behaviors are for a Racket test module and what breaks when tests misbehave. This doesn't have to be `rackunit`...
This would allow `raco test` to know when not all tests were run for whatever reason. Tests that are skipped in the package build server (e.g. tests requiring an internet...
Closes #47 This PR adds the following checks: - `(check-fail )` - asserts that `` evaluates a failing check and that the check failure exception satisfies `` in the same...
Using test suites causes `raco test --drdr` to report all tests as coming from the module where `run-tests` is called. The tests don't really need any of the features that...
Currently, the internal representation of test suites has a notion of a "seed", which is threaded throughout the test by means of a complex and indirect chaining of lambdas and...
Since custom checks aren't functions, they can't be protected by `contract-out` without disabling their location-capturing capabilities. A `check-out` provide form that allows contracts to be added could work like this:...
As mentioned in #14, it's very difficult to test custom RackUnit checks. This issue proposes some additional checks for RackUnit to improve the situation ### The checks - `(check-fail (lambda...
Given this program: ```racket #lang racket (require rackunit) (test-case "foo" (test-case "bar" (check-equal? 1 2))) ``` The output is: ``` -------------------- bar FAILURE name: check-equal? location: unsaved-editor:5:4 actual: 1 expected:...
`define-check` and `define-simple-check` only allow positional arguments without defaults to be provided. If checks are meant to be semantically procedures, they should accept the same arguments as procedures.