[
https://jira.jboss.org/jira/browse/JGRP-850?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on JGRP-850:
------------------------------------------
OK. After discussion with Bela, despite the fact that we have had no response from Beust
& Co regarding the registration of the listener, we will go ahead and use a patched
version of testNG and apply the changes to JUnitXMLReporter to fix the output leak.
1. Downloaded the latest testNG (revision 645) from its repo:
This revision incorporates the fix to timeout processing which Vladimir needed.
2. Modified testNG.java as described earlier to fix the registration of the listener.
3. Built testNG using jdk 1.5.0_14
ant dist
mv testng-5.8.1beta-jdk15.jar testng.jar
4. Copied into the JGroups lib directory.
6. Ran the functional, udp and tcp testsuites to see if all seems ok. Test results the
same in modified and non-modified versions of JGroups distribution.
6. Committed the new JUnitXMLReporter and testng.jar to the repository.
Fix output leak in testNG test reporting
----------------------------------------
Key: JGRP-850
URL:
https://jira.jboss.org/jira/browse/JGRP-850
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Priority: Minor
Fix For: 2.7
org.jgroups.util.JUnitXmlReporter is a class which takes output from testNG test cases
and prepares xml test case reports in JUnit-compatible format. These xml files are then
used to generate JUnit style reports.
At present, output from test case methods which execute before the main test case (testNG
configurator methods, such as @BeforeSuite, @AfterSite, etc) written to System.out and
System.err is leaking to the console and not being captured with the rest of the testNG
output.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira