On Sep 9, 2007, at 1:15 AM, Ovid wrote:
--- Matisse Enzer <[EMAIL PROTECTED]> wrote:
A side-note to keep in mind: If we every want to be able to convert
TAP to the XML format produced by the JUnit ant task (this way for
example CruiseControl could more easily read the results of Perl
tests) then it becomes desirable to get timing info for each perl
test - that is, each ok(), is(), is_deeply(), etc.
Are you sure about that? In jUnit, each "test" is a method which
contains a number of individual assert. In Perl, those asserts are
individual tests.
yes I know - TAP doesn't have the same number of levels of hierarchy
that xUnit does, but i believe that the closest match, if one wanted
to run perl tests and produce xUnit-style XML output would be to
treat Perl 'tests' (i.e. assertions such as 'ok') as what xUnit calls
'tests'
There certainly is a mapping problem and I don't have a perfect
solution, and enabling Perl test output to be understood by
CruiseControl (for example) is a valuable thing, in my opinion.
-M
-------------------------------------------------------
Matisse Enzer <[EMAIL PROTECTED]>
http://www.matisse.net/ - http://www.eigenstate.net/
