In article <[EMAIL PROTECTED]>, Eric Wilhelm <[EMAIL PROTECTED]> wrote:
> # from Andy Armstrong > # on Wednesday 31 October 2007 16:51: > > >But what about a more general mechanism? A TAP directive that means > >'schedule these other tests'. So then you'd have a controller test > >which was the only one directly visible to Test::Harness and that'd > >decide which other tests to run. > > It sounds like it would be re-creating a lot of the same functionality > needed for declarative extra testing and/or Test::Manifest. I don't care if Test::Manifest gets folded into the new stuff, even if re-implemented. If I can do the same thing with the core test modules I don't need Test::Manifest anymore. :) Test::Manifest can do this though. I list tests in t/test_manifest, which doesn't have to exist until `make test` time. In t/test_manifest, there is an ;include directive to include other files that have other lists of tests, recursively. There's also a way to mark test levels, so I can run all tests at level 1, or level 2, or whatever without worrying about which diretories or names there are. All that stuff is unconnected to the structure of t/.
