generated testng-failed.xml does not conform to DTD

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Any time a test fails (i.e. whenever testng-failed.xml is created)

What is the expected output? What do you see instead?

Expected:

<suite thread-count="5" verbose="1" name="Failed suite [test-project]" 
annotations="JDK">

Actual:

<suite thread-count="5" verbose="1" name="Failed suite [test-project]"
junit="false" annotations="JDK">

In other words, junit is not a valid attribute to suite according to the DTD.

What version of the product are you using? On what operating system?

TestNG 5.6
JDK 1.5.11 (windows), JDK 1.5.?? (OS X)
Eclipse 3.3

Please provide any additional information below.

Original issue reported on code.google.com by scottspe...@gmail.com on 4 Jul 2007 at 4:43

[GoogleCodeExporter]

It gets worse in 5.7.  In TestNG 5.6, the "junit" attribute shouldn't be used 
on a suite.

In TestNG 5.7, both the "skipfailedinvocationCounts" and "junit" attributes are 
invalid.

Original comment by sst...@gmail.com on 11 Apr 2008 at 10:51

[GoogleCodeExporter]

"In TestNG 5.7, both the "skipfailedinvocationCounts" and "junit" attributes are
invalid."

The problem persists in 5.8.

Original comment by bowserm...@gmail.com on 21 Oct 2008 at 6:45

[GoogleCodeExporter]

I have same problems with junit and skipfailedinvocationCounts attributes of 
suite
element.
The javadoc of the XmlSuite class says that these attributes are valid so it's 
just a
matter of updating the DTD.

http://testng.org/javadocs/org/testng/xml/XmlSuite.html

I fixed the DTD and improved it by adding an attribute-flag definition and 
default
values for boolean fields.
I considered that a boolean attribute could be either "true" or "false", feel 
free to
add other values like "yes", "no".

Please consider including this attached DTD in a future release.

Original comment by gael.mar...@gmail.com on 28 Nov 2008 at 5:33

Attachments:

• testng-1.0.dtd