On Wednesday 04 April 2007 11:41, Eric Wilhelm wrote: > # from chromatic
> >It seems to me that we already have a good way of separating tests per > > their behavior: separate test files and even separate test > > directories. > Correct. See my other post and the test profiles thing in > Module::Build. > What I was thinking of here was more along the lines of how to get > Test::Class to play that game. There's no reason a test class has to mimic the tested code's hierarchy and separation of concerns. The same principles of good OO design apply to test classes as well. If it's difficult to do the things you want to do with a monolithic test file or test class, split it along functional lines--the same way you'd split a module or a class. -- c
