Gary King <[EMAIL PROTECTED]> writes: > Here are some ideas for the sorts of things by which a test framework > can be measured (this is on the ALU page too). > > * Interactive versus batch. > * Supports hierarchical test organization > * Supports setup and teardown > * Verbosity > * Lisp integration (in a touchy feely way [smile]) > * Special support for errors, warnings, and conditions > > Please chime in to improve...
Hello, chiming in here with my first post, based on some recent experience looking for a simple testing library. * Supports test-first[1] development So, for example, you can write tests for functions that haven't been written yet. Rather than drop into the debugger, the framework reports this as a failed test. * Need to reload tests after changes? When testing macros, can you change the macro definition without reloading the tests? If the tests are compiled, the answer is no. If tests are stored as unevaluated S-expressions (as in LispUnit[1], to name one example) the answer is yes. This leads to... * How tests are stored Classes, lambdas, S-expressions,... -Stuart [1] http://www.extremeprogramming.org/rules/testfirst.html [2] http://www.cs.northwestern.edu/academics/courses/325/readings/lisp-unit.html _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
