On 1 Nov 2007, at 21:22, brian d foy wrote:
# t/controller.t use Test::Steering;include ('xt/frob') if frob_avail(); include ('xt/slow') if all_the_time_in_the_world();That would happen at `make test` time (or whatever M::B does)?
That's what I envisaged, yes. The harness would run t/controller.t which would spit out some TSP and in response to that the harness would schedule additional tests.
When I want this sort of thing with Test::Manifest, I create t/test_manifest at `make time`. It might be interesting to reflect on the harness though, and write to the test queue. I don't think I need this. I just wanted to say "reflect" :)
Good work :)
use Test::Harness; add_test_file( 'foo.t', AT_END ); # or NEXT, or whatever
Well that's pretty much what I have in mind. TSP isn't imperative - it doesn't cause a test to be run immediately - it causes tests to be added to - or perhaps removed from the harness's queue.
-- Andy Armstrong, Hexten
