# from Ovid # on Friday 12 December 2008 04:37: >Running a single test means that I ... want to run that test. >... Here are conditions I see crop up in tests: > POD_COVERAGE ... FAST_TESTS ... PROFILE_TESTS > ... >doesn't (and usually shouldn't) know if other tests are being run ... > >... "prove" shouldn't have special-case knowledge ... > >... but I don't know if anyone else would benefit or if this is the > right approach.
This is exactly the sort of thing I was getting at when we had the discussion about the xt/ directory. If the harness can be made to decide which tests to run based on some external configuration, then the test script is not making any decisions internally. I don't think the harness setting an ENV is the way to go, because then you'll have to code more logic into each test script, which begets copy+paste coding. It also means the test script has to contain a few more lines of "off-topic" meta logic which the programmer must continually skim past. The external config is a bit more complicated because you have a slightly hidden source of behavior. But, strictly speaking, you don't actually need it if you just put the extra tests in xt and get a habit of running `prove t xt`. http://scratchcomputing.com/tmp/extra_testing.txt http://www.nntp.perl.org/group/perl.qa/2007/10/msg9405.html --Eric -- "It ain't those parts of the Bible that I can't understand that bother me, it's the parts that I do understand." --Mark Twain --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------
