In article <[EMAIL PROTECTED]>, Adriano Ferreira <[EMAIL PROTECTED]> wrote:
> On 8/17/07, brian d foy <[EMAIL PROTECTED]> wrote: > > In article > > <[EMAIL PROTECTED]>, Adriano > > Ferreira <[EMAIL PROTECTED]> wrote: > > ...smells a lot like Test::Manifest, which is just test. In > > t/test_manifest, you just list the files that you want. Optionally, you > > can set a test level and mark some tests only happening at certain > > levels. > The only drawback is redundant information: there are the tests and > the list of tests. Keeping tests in "t/" with some fine way to > discover what they are good for (according to Chris' idea) may be > promising if not too magical. I've yet to provide the "make testmanifest" homolog to "make manifest" because so far I just `find . -name "*.t" > test_manifest". There is a bit more work to maintain that, but it's a small bit of work to the current alternatives, especially when I want to repeatedly run a subset of tests by replacing test_manifest temporarily. Even if people don't like Test::Manifest, the solution is probably the same for any other suggestions: override parts of Test::Harness to discover the file names you want to test, or override runtests. Those are both very short routines that hand off things to the heavy lifters.
