Re: Combining TAP with more extensive logging of raw data

2009-06-12 Thread Steffen Schwigon
Andy Armstrong a...@hexten.net writes: On 10 Jun 2009, at 09:33, Gabor Szabo wrote: So now that I am switching reporting to TAP how do I log the raw data? This is the primary use case for TAP diagnostic blocks. Unfortunately I don't think any TAP emitter currently supports TAP diagnostics

Re: Combining TAP with more extensive logging of raw data

2009-06-11 Thread Ovid
- Original Message From: Michael G Schwern schw...@pobox.com Gabor Szabo wrote: I recall that we talked about a possibility to emit yamlish but the last thing I remember was the discussion about lower or upper case names... Was there a progress in that subject ? tl;dr

Re: Combining TAP with more extensive logging of raw data

2009-06-11 Thread Michael G Schwern
Ovid wrote: Yeah, I can deal with all of this. I think the main thing is that any YAML diagnostics which accept arbitrary keys added will have to: a. Reject any key matching /^[[:lower:]]/ (or is /^[a-z]/ really preferred here?) The simple ASCII/UTF8 a-z avoids wacky locale issues which

Combining TAP with more extensive logging of raw data

2009-06-10 Thread Gabor Szabo
I am trying to switch some home grown test scripts to test scripts using Test::* modules and TAP. There is one major issue and I wonder how others deal with it. The home grown test scripts include raw data in their reports. e.g. when testing a web services we send an XML and receive another

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Michael Peters
Gabor Szabo wrote: How do you deal with similar situation ? Test::More::Diagnostic lets you output structured YAML with your tests. Not all of the tools in the chain understand this YAML, but those that don't should ignore it equally. It's part of the spec (at least loosely) so it will be

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Ovid
- Original Message From: Michael Peters mpet...@plusthree.com How do you deal with similar situation ? Test::More::Diagnostic lets you output structured YAML with your tests. Not all of the tools in the chain understand this YAML, but those that don't should ignore it

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Andy Armstrong
On 10 Jun 2009, at 09:33, Gabor Szabo wrote: So now that I am switching reporting to TAP how do I log the raw data? This is the primary use case for TAP diagnostic blocks. Unfortunately I don't think any TAP emitter currently supports TAP diagnostics :) Test::Harness does process YAML

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Andy Armstrong
On 10 Jun 2009, at 14:07, Michael Peters wrote: Gabor Szabo wrote: How do you deal with similar situation ? Test::More::Diagnostic lets you output structured YAML with your tests. Not all of the tools in the chain understand this YAML, but those that don't should ignore it equally. It's

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Ovid
- Original Message From: Andy Armstrong a...@hexten.net Test::More::Diagnostic lets you output structured YAML with your tests. Not all of the tools in the chain understand this YAML, but those that don't should ignore it equally. It's part of the spec (at least loosely) so it

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Gabor Szabo
On Wed, Jun 10, 2009 at 5:57 PM, Andy Armstronga...@hexten.net wrote: On 10 Jun 2009, at 14:07, Michael Peters wrote: Gabor Szabo wrote: How do you deal with similar situation ? Test::More::Diagnostic lets you output structured YAML with your tests. Not all of the tools in the chain

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Michael Peters
Gabor Szabo wrote: I recall that we talked about a possibility to emit yamlish but the last thing I remember was the discussion about lower or upper case names... Was there a progress in that subject ? I'm not entirely sure it was resolved, but we tend to follow cow-paths through these

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Ovid
- Original Message From: Gabor Szabo szab...@gmail.com I am quite confused and I am not sure what do I really want :-) I recall that we talked about a possibility to emit yamlish but the last thing I remember was the discussion about lower or upper case names... Was there a

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Michael G Schwern
Gabor Szabo wrote: So now that I am switching reporting to TAP how do I log the raw data? So far I could think only to either create a log file with the raw data or to print the raw data using diag(). In the former case I lose the single result file advantage and I'll have to somehow

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Michael G Schwern
Andy Armstrong wrote: On 10 Jun 2009, at 16:12, Ovid wrote: I can probably make a release that does within a few days if that's the kind of thing that Gabor needs. If we can get buy-in from Schwern, what about forking https://github.com/schwern/test-more/tree and adding it there? It would

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Michael G Schwern
Gabor Szabo wrote: I recall that we talked about a possibility to emit yamlish but the last thing I remember was the discussion about lower or upper case names... Was there a progress in that subject ? tl;dr version: Yes, its resolved at least to Ovid and I's satisfaction who were the two most

Re: Combining TAP with more extensive logging of raw data

2009-06-10 Thread Michael G Schwern
Gabor Szabo wrote: Anyway here is another thing that I found. The test script fetches a few rows from a database and prints out a nicely formatted table of the values using high quality ascii art: 1 | 3 | foo 1 | 7 | bar I can just print the array holding this using explain