On 8/22/06, Christopher D. Malon <[EMAIL PROTECTED]> wrote:
On Aug 22, 2006, at 9:55 AM, Agent Zhang wrote:
> Well, in short, we have divided the .t files in the Pugs test suite
> into pieces and inserted every resulting snippet after the
> corresponding paragraph of the Synopses.
This is really, really cool. Thanks!
Glad you like it. :)
Often people read the synopses and wonder, "Is feature X from the spec
working in Pugs today?" I think it would be cool to integrate the smoke
reports with your inlined tests in the synopses. When a test section is
displayed, lines from the test that pass could be colored green,
and those that fail or are todo could be red. The "show snippet"
link might itself be colored, too.
Yes, the good old util/catalog_tests.pl does color the tests with
green and red, and Gaal has also asked me if I'm planning to implement
that feature in util/smartlinks.pl. I'd say "of course", b0ut I intend
to make this feature optional, since just as you have said, smoke
results are implementation specific while tests and docs are not.
Of course, this idea doesn't quite make sense, because test status
depends on which runtime is used (and sometimes which O/S is used).
Maybe we could produce one version of the synopsis for
each runtime/OS combination listed in smoke.pugscode.org, and update it
as new smoke reports come in. (Even this approach needs more thought:
do we mix results from different smoke reports if a new report comes in
that skips a lot of tests?)
Yeah, that will be even cooler. Thank you for this wonderful
suggestion. However, I'm afraid it is not of very high priority for me
given the current status of the smartlinks. Among other things, I'll
focus on polishing the Pugs test suite as well as the smartlinks used
in it so as to get every group fo tests and every Synopsis paragraph
linked. Of course, if you have the tuits to try that, I'll be
delighted.
Do you think this is worth trying, or would you rather keep the
smokes separate?
This is definitely worth trying. :=)
Regards,
Agent
