Process raw TAP output from STDIN

[timgimyee]

For #41.

[Leont]

But how to process TAP streams that don't start with 1..X?

[timgimyee]

Just read TAP13 specs. Looks like the 1..N plan line is optional, and just a single ok or not ok is valid. Will need to check for these.

[Leont]

TAP can start with:

• A plan
• A version line
• An ok/not ok line
• A comment
• A subtest line

I think that in that light a heuristic becomes quite fragile.

[Leont]

I think that should be \d+, otherwise it would fail to match 1..10

[timgimyee]

Code is only as good as tests. Good catch.

[arc]

This seems like a fragile approach to me. I'd prefer the "parse stdin" mode to be enabled with a new option to prove.

[Leont]

This seems like a fragile approach to me. I'd prefer the "parse stdin" mode to be enabled with a new option to prove.

Agreed

[timgimyee]

An explicit option would be more robust.

[arc]

I was imagining the option would replace the heuristic parsing, rather than being an alternative to it. I think heuristic parsing of any sort is likely to cause problems, and Test::Harness risks being bound by backcompat with those problematic aspects.