On Sun, Jun 01, 2008 at 05:20:40PM +0100, Ian Lynagh wrote: > On Sat, May 31, 2008 at 03:21:20AM -0700, David Roundy wrote: > > > > > Thu May 29 02:53:09 BST 2008 Ian Lynagh <[EMAIL PROTECTED]> > > > * Make Darcs.Patch.Unit export a runnable main > > > > I see no reason for this patch. Why not just use our existing driver > > program? > > I probably just didn't see the program.
Ah, it's called unit. make test_unit compiles and runs it. > > > Thu May 29 12:49:52 BST 2008 Ian Lynagh <[EMAIL PROTECTED]> > > > * Handle exceptions in the unit tests > > > > This looks like a regression to me. When we fail with an exception, > > quickcheck 2 catches this exception and displays it along with the input > > that triggered the exception. > > I definitely had problems where exceptions weren't being caught. Is > quickcheck used to run the tests that looks like unit tests (where it > doesn't tell you how many passed), e.g.: > Testing real merge output consistent > ? No, we don't use quickcheck for those. But the place to catch exceptions would be in the driver, not the test. -- David Roundy Department of Physics Oregon State University _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
