David Storrs wrote on 11/8/18 11:10 AM:
Will test successes show output as well? For me that's the hard stop
on using RackUnit -- the fact that it shows nothing on success means
that there's no way to tell the difference between "everything ran and
passed", "some things ran and passed but
On Wed, Nov 7, 2018 at 3:45 PM Neil Van Dyke wrote:
> Greg Hendershott wrote on 11/6/18 9:56 AM:
> > I'd suggest writing to stderr the same location format used by rackunit.
>
> OK, thank you (and David Storr). I looked at the current RackUnit. How
> about the following proposal?
>
> Proposal:
Greg Hendershott wrote on 11/6/18 9:56 AM:
I'd suggest writing to stderr the same location format used by rackunit.
OK, thank you (and David Storr). I looked at the current RackUnit. How
about the following proposal?
Proposal: A test failure message is a one-line message that:
* in
On Fri, Nov 2, 2018 at 3:38 PM Neil Van Dyke wrote:
> * Should such a failing message also have some way of click navigating
> to the test failure in DrRacket, like for exceptions? (Note that the
> answer to the next might be involved.)
Yes please! It is no fun finding a failing test source in
On Fri, Nov 2, 2018 at 3:38 PM Neil Van Dyke wrote:
> Anyone have info or preferences on what are good output conventions for
> Racket package embedded unit tests? (For use with all of: `raco test`,
> package catalog and other builds, DrRacket and other IDEs?)
>
> I intend to reimplement
Anyone have info or preferences on what are good output conventions for
Racket package embedded unit tests? (For use with all of: `raco test`,
package catalog and other builds, DrRacket and other IDEs?)
I intend to reimplement Overeasy
("https://www.neilvandyke.org/racket/overeasy/;) in a
6 matches
Mail list logo
