On 5 Apr 2007, at 11:01, Eric Wilhelm wrote:
I think I'd rather put my tests into subdirectories to group them -
That only gets you the ability to run some of them at once, not the
ability to *not* run some of them without special action.
You could just
$ runtests -b t/Somedir/*.t t/Otherdir/*.t
I suppose.
but either way that only gets you a single taxonomy. In practice
you're quite likely to want tests to be classified in more than one
way.
True. I'm interested in pursuing that. As I said, possibly an
environment variable with some YAML to tell the producer what to skip
or thereabouts. As chromatic pointed out, it does potentially add
quite a bit of complexity.
I guess I should have said "if you want your tests classified at all
you might not want to stop at a single classification".
It doesn't need to be part of TAP::Harness I think. T::H should make
it easy to write, for example, TAP::Harness::Classified.
I'm pretty certain it doesn't involve command-line arguments for tests
though.
No - the two issues were conflated by my choice of example I think. I
can certainly think of other reasons for passing arguments to tests
but you can, of course, do the same thing with env variables - and
that has the benefit of working right now :)
--
Andy Armstrong, hexten.net
