On Tue, 2005-03-08 at 11:40 -0800, Michael G Schwern 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. > > By default, everything looks the same to using modules, except that the > > level trickery can go away, mostly. It should be easy to swap out > > TestRun and Counter and TestResults within the current Test::Builder > > object temporarily, in the case of wanting to run a lot of subtests > > without increasing the number, for example. > > So how does it handle these scenarios. > > * Testing a test module. Change the output object to something you control. > * Altering the behavior across all modules used in the process. I'm not sure. What's the use case? > * Altering the behavior for just one module. Subclass Test::Builder? Pass arguments to its constructor naming different other classes to use? -- c
