Markus Galli is in the Software Composition Group at the University of Berne, and is going to tell us about better unit testing strategies. He's had a lot of experience in this area. The goal: facilitate the navigation between tests and methods, and improve the composition of complex test scenarios.

The root of the taxonomy focuses on this question - does a test focus on one method? A One Method test - "tests the outcome of exactly one call of a method under test". A data point - 53% of the Squeak tests are of this sort.

On Method Test Suite - tests the outcome of a single method under many circumstances. Again, in Squeak, 15% fall here.

2% are Pessimistic Methods - checks that an exception is thrown if a method's preconditions are not met.

Most of the rest fall into Mutiple Method Commands - although most of those can be refactored into single method tests of one sort or another.

MultiFacet test suite - reuse a test scenario to test several candidate methods - 2% of Squeak test methods fall here.

Cascaded Test Suites - decomposable into One Methid tests. 4% of Squeak tests hit here.

Constraint Test - also decomposable. checks the interplay of several methods w/o focusing on any one. 10% of Squeak tests fall here.

Cascaded Test Suite - results of tests are used to set up other tests. Decomposable.

He's demonstrating some tools (5 pane browsers, etc.,) - but I'm just too tired to follow it all...