[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Chicken-users] Re: egg unit testing

From: Kon Lovett
Subject: [Chicken-users] Re: egg unit testing
Date: Fri, 8 Dec 2006 07:56:26 -0800

Hash: SHA1

On Dec 8, 2006, at 7:38 AM, Ivan Raikov wrote:

  Well, it's certainly not going to hurt anybody, and it might be
somewhat useful for future "forking" of the egg repository. Though of
course some eggs might later have bug fixes that don't necessarily
break compatibility with older versions... whatever happened to the
idea of having unit tests for eggs?

Working on it. The unreleased version of 'test-infrastructure' (ver 2.0) has almost all the features necessary for batch testing. Missing are system resource limits (rlimit) statements & a test runner process (the largest collection is at the level of ".scm" of tests for now; being able to state sets of ".scm" would be nice).


Thread safety. All global variables removed.
Smaller macro expansion.
Lower overhead.
Source expansion control API.
Test procedure definition syntax.
Anonymous test definition syntax.
*test-package & *test-case short forms. Replaces test-group.
Test procedure state API.
Test result filtering.
Immediate test result output. (stream of tagged alist to stdout)
The '() will be ignored as a WARNING.
Better testeez support

But I have issues w/ the source expansion philosophy of Peter Keller's original, which I never changed. I would like to do the following:

- - Switch to a minimal source expansion method

- - Remove syntax-case requirement. i.e. add non-hygienic versions of the macros

- - Then I guess rename the thing "test-base"

Version: GnuPG v1.4.5 (Darwin)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]