FWIW...
I was inspired by our test authoring, the other night.
These days, I prefer to test-drive my code. So, I asked the question, "what core functionality are we expecting from Rulers, at this point?" and then wrote the minimal set of tests that describe that functionality.
I am playing with splitting the class definition up so that the corresponding mock controllers are physically next to the test case methods that use them (rather than force you, the reader, to hunt for them elsewhere in the file).
I know I like this, but what matters is how it reads for others...
Question: do you find this way of organizing the test class readable? (as compared to having all the test methods in one "class" declaration)