DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43969>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43969


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Additional Comments From [EMAIL PROTECTED]  2007-11-27 02:33 -------
Dan,

as discussed on testng-user, this is because the current xml+report is junit3.x
era. I am willing to extend it to support junit4, testng, antunit,
smartfrog-xunit tests, etc, as long as we can do this without breaking :
CruiseControl, Hudson, et al. 

Let's start by creating a wiki entry and listing 
 -tools/products that generate the report
 -tools/products that process the XML it generates
 -features wanted 
 -test plan

Can I also point you at
http://smartfrog.org/presentations/distributed_testing_with_smartfrog_slides.pdf
and
http://smartfrog.org/autolinks/googleLTAC06.htm

where I show a prototype XHTML format that can be streamed out and is readable
before the tests have finished. Moving to something like that would break
everything, so I'm not going to propose it. But I would like to enable better
streaming, by pushing all new summary information out as elements and not
attributes on root nodes. 

I'd like something such as


<testsuite total="1">
  <metadata>
    <description>Tests of OS-specific things</description>
    <xml>
     <rdf xmlns:rdf="http://w3c.org/rdf";>
      <!-- random triples here -->
     </rdf>
    </xml>
  </metadata>

 <testcase name="testIgnorable">
   <metadata>
     <description>A test that only works on Win98</description>
     <links>
       <uri>http://svn.example.org/ex/4</uri>
     </links>
     <tags><tag>win98</tag><tag>windows</tag><tag>trouble</tag></tags>
     <issues>
       <id>JIRA-117</id>
       <id>JIRA-113</id>
     </issues>
    </metadata>
    <skipped>
     wrong OS
    </skipped>
  </testcase>
  
 <summary>
  <total>1</total>
  <skipped>1</skipped>
 </summary>

</testsuite>

1. new summary data goes in at the end. If you want to handle skipping, embrace
the new format

2. extra stuff goes into a metadata corner. This is all static with every test.
I'd like everything needed to create interesting Atom feeds.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to