Bill Venners wrote on 24.8.2010 0:00:

There's this line which passes the context to the test, so that the test
will know that which tests to execute on the current test run, and the
initialization in the Context.bootstrap() method:
http://github.com/orfjackal/specsy/blob/master/src/main/scala/net/orf...

It would be possible to detect when the class is instantiated the first
time by the framework (when no context has been prepared), but having to
deal with that special case would complicate the code needlessly. It
leads to a cleaner design when the test runner is separated from the
test class. Now calling the root spec (the test code in the constructor)
can be handled the same way as calling the nested specs - in
http://github.com/orfjackal/specsy/blob/master/src/main/scala/net/orf...
the bootstrap() method is for the root spec and the specify() method for
the nested specs - the only differences relate to changing the running
status.

Probably also writing tests for the testing framework code would be
harder, if the test runner would be coupled with the test class. Now I
can test the framework by just passing closures to the test runner (for
example
http://github.com/orfjackal/specsy/blob/master/src/test/scala/net/orf...)
instead of having to creating a dummy class whose constructor contains
the test code. There are only a couple of tests (for the JUnit runner
and the code itself which instantiates the classes) which require
concrete dummy classes as test data.

I suppose it basically boils down to this:
http://michaelfeathers.typepad.com/michael_feathers_blog/2010/08/test...

Yes, that's how I do it. See the chapter "Before" and "After" Blocks in
http://github.com/orfjackal/specsy#readme

Specsy's documentation (http://github.com/orfjackal/specsy#readme) is
only about 4 pages long and it consists mostly of code examples (the
most valuable kind of documentation). I'm expecting everybody to read it
before using the framework.

--
Esko Luontola
www.orfjackal.net