We should really smoothen the path from the test engine to the unit
testing framework. -- Matthias
Begin forwarded message:
From: Matt Jadud <jad...@gmail.com>
Date: April 23, 2009 7:20:37 AM EDT
To: mat...@udel.edu
Cc: plt-sch...@list.cs.brown.edu
Subject: Re: [plt-scheme] Newbie help using (check-expect): problem
nesting (generate-report)
On Thu, Apr 23, 2009 at 1:11 AM, <mat...@udel.edu> wrote:
Instead of just listing a whole lot of (check-expect) expressions
all serially one after another,
and then evaluating them all when I run the code, I was hoping to
be able to do something like
this:
Hi Mattdz,
Does this help at all?
http://www.rockalypse.org/courses/cmpsc220sp09/resources/
unit_testing_in_plt_scheme.html
You might, in short, try using SchemeUnit. It isn't far off from where
you're at, and it lets you write your tests in test suites, which you
can then combine into larger suites and run. (Or, you can run
individual suites.) Also, you can "define-simple-check", which lets
you write your own checks.
The documentation for SchemeUnit is good, and you're welcome to ask
questions about it here. There is also the possibility that someone
will chime in and tell you how you can go about this using the tools
you're already using.
The transition from one to the other should be minor/painless, though,
so I don't think I'm leading you vastly astray by suggesting
SchemeUnit.
Cheers,
Matt
_________________________________________________
For list-related administrative tasks:
http://list.cs.brown.edu/mailman/listinfo/plt-scheme
_________________________________________________
For list-related administrative tasks:
http://list.cs.brown.edu/mailman/listinfo/plt-dev
