pe, 2009-07-03 kello 11:39 +0200, Peter Pöschl kirjoitti:
What about emitting this as TAP, the Test Anything Protocol [1]?
That is a very interesting suggestion. I don't think it looks very good
for human consumption, but I would love to have a plugin to optionally
produce it for situations
Lars Wirzenius l...@liw.fi writes:
How would _you_ like to see piuparts report results, and produce other
output? Go wild, the sky is bright blue.
The obvious things to fix are:
- make it really easy to see what the result of each test is
Almost as obvious is to easily identify
Peter Pöschl pp2ml.deb0...@nest-ai.de writes:
What about emitting this as TAP, the Test Anything Protocol [1]?
+0 from me.
Investigating TAP is on my to-do list, so I don't have an opinion on
that yet; but in principle it seems fine, and there is goodness in
widely-used output formats.
--
\
Lars Wirzenius l...@liw.fi writes:
How would _you_ like to see piuparts report results, and produce other
output? Go wild, the sky is bright blue.
The obvious things to fix are:
- make it really easy to see what the result of each test is
Almost as obvious is to easily identify which
2009/6/20 Lars Wirzenius l...@liw.fi:
I'm thinking about changing the way piuparts outputs results. At the
moment it outputs a log file that contains everything it does, and
buried deep in that is the test results. This tends to work badly.
[...]
How would _you_ like to see piuparts report
Jens Peter Secher j...@debian.org writes:
2009/6/20 Lars Wirzenius l...@liw.fi:
I'm thinking about changing the way piuparts outputs results. At the
moment it outputs a log file that contains everything it does, and
buried deep in that is the test results. This tends to work badly.
[...]
Hi,
I'm thinking about changing the way piuparts outputs results. At the
moment it outputs a log file that contains everything it does, and
buried deep in that is the test results. This tends to work badly.
I have some ideas for how things should work, but before I start working
on them, I'd
7 matches
Mail list logo
