Tap Version Number
# from Andy Armstrong # on Friday 09 March 2007 04:47 pm: I'm just adding support for specifying the TAP version number[1] to TAPx::Parser. It seems reasonable that the version, if present, should be the first thing in the TAP. I think that should always be the case. While I don't forsee needing to do it differently, I think it's safe to assume: if we ever need to break that for some reason, then it's a newer version of TAP. Taking that logic a step further, I vote YAGNI on the complete syntax for meta-information bit. If we need more syntax, we bump the version and continue on our merry way, right? Is anybody itching for more metadata right now? I figure we should keep including this link in every mail until everybody has read it so many times that they start complaining :-) http://perl-qa.yi.org/index.php/TAP_version --Eric -- Everything should be made as simple as possible, but no simpler. --Albert Einstein --- http://scratchcomputing.com ---
Re: The most important TAP tasks.
On 9 Mar 2007, at 23:17, Michael G Schwern wrote: *) A TAP version http://perl-qa.yi.org/index.php/TAP_version Before we add any TAP extensions we need a way to identify what version of TAP we're outputting. Discuss and implement. Done. The supported syntax is as per that page. In the absence of a version it defaults to 3. It's impossible to explicitly set a version 4. -- Andy Armstrong, hexten.net
Re: Tap Version Number
Eric Wilhelm wrote: I think that should always be the case. While I don't forsee needing to do it differently, I think it's safe to assume: if we ever need to break that for some reason, then it's a newer version of TAP. Taking that logic a step further, I vote YAGNI on the complete syntax for meta-information bit. If we need more syntax, we bump the version and continue on our merry way, right? Right. Is anybody itching for more metadata right now? Yes, but that's a wholly different thing and should not be lumped in with the TAP version.
Re: The most important TAP tasks.
Andy Armstrong wrote: On 9 Mar 2007, at 23:17, Michael G Schwern wrote: *) A TAP version http://perl-qa.yi.org/index.php/TAP_version Before we add any TAP extensions we need a way to identify what version of TAP we're outputting. Discuss and implement. Done. The supported syntax is as per that page. In the absence of a version it defaults to 3. It's impossible to explicitly set a version 4. I'm counting back through TAP changes and I'm up to version 6. I'll do a final sweep through the changes to t/TEST and Test::Harness to find out what else was added so we can solidify this for historical purposes. Or we can just declare the version that introduces TAP version to be 10 and backfill the rest later.
Re: The most important TAP tasks.
On 10 Mar 2007, at 22:57, Michael G Schwern wrote: I'm counting back through TAP changes and I'm up to version 6. I'll do a final sweep through the changes to t/TEST and Test::Harness to find out what else was added so we can solidify this for historical purposes. Or we can just declare the version that introduces TAP version to be 10 and backfill the rest later. It'd be nice to avoid a gap unless it's a major hassle. -- Andy Armstrong, hexten.net
A little wiki work.
I've done a bit or work on the Wiki. The TAP proposals have been grouped into ones that are considered worth implementing, ones that are still ideas and ones that have been rejected / supplanted. Don't like the decisions I made? Edit it, its a wiki. I've also written out a proposal for the test meta information. This covers both the desires to output information about the environment (time, date, perl version, environment variables...) and about the status of the test. It goes at the beginning and end of the test. It uses the same basic format as the Test Diagnostics proposal. All fields are optional. http://perl-qa.yi.org/index.php/Test_meta_information TAP version 9 --- datetime: Sat Mar 10 16:04:50 PST 2007 producer: name: Test.pm version: 1.23 ... 1..2 ok 1 ok 2 --- exit: 0 wait: 0 times: cpu: 4.1 sys: 1.0 real: 6.5 database: 0.3 ...
