On Tue, Mar 08, 2005 at 12:09:02PM -0800, chromatic wrote: > > > Test::Builder::TestResults - the parent class for all types of tests > > > (pass, fail, todo, skip). This may be too much detail here, but I like > > > the idea of these knowing how to format themselves for output. > > > > Dunno what this is for. > > Maybe it's unnecessary now. It's likely more valuable in a refactoring > of Test::Harness::Straps.
Allow me to amplify: Huh? I don't get what you mean. At all. > > So how does it handle these scenarios. > > > > * Testing a test module. > > Change the output object to something you control. Trouble is now you need two simultaneous testing instances. One for the Test module you're testing with its output redirected and its own test counter. And one to test the Test module with its output set normally and its own test counter. > > * Altering the behavior across all modules used in the process. > > I'm not sure. What's the use case? Off the top of my head... changing the testing behavior so its exit on failure XUnit style rather than continuing to run. Another might be additional reporting of TODO tests. Basically I'm groping around for corner cases where another singleton might be needed. > > * Altering the behavior for just one module. > > Subclass Test::Builder? Pass arguments to its constructor naming > different other classes to use? Ok, that's covered by the "every module has its own TB instance". Good.
