ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 7245] New: - JUnit & JUnitReport tasks / VM constraints
Date Tue, 19 Mar 2002 14:18:54 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7245>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7245

JUnit & JUnitReport tasks / VM constraints

           Summary: JUnit & JUnitReport tasks / VM constraints
           Product: Ant
           Version: 1.4.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Optional Tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: fabrice_carnet@users.sourceforge.net
                CC: sbailliez@apache.org


Hi, 

I use the JUnit Ant task with fork mode="on", because I want the JUnit tests to 
run in another VM than the build. For performance reasons (4 mins to run all 
the tests instead of 30 mins), I use the same VM to run all the tests (this 
avoid initializing the class instances with their configuration for each test).
So to meet these goals, I use the JUnit task with a single entry point : a test 
suite that browses recursively in all the packages all the tests.

The problem is that I would like to use the JUnitReport task to build an HTLM 
report. But the XMLJUnitResultFormatter makes in my case a single XML document 
which can't be used with the JUnitReport task because the XML doesn't have the 
test package & class information :

<testsuite name="org.na.tests.AllTests" tests="267" failures="0" errors="0" 
time="215.123">
...
	<testcase name="testDefaultLanguage" time="30.885"/>
	<testcase name="testRetryAuthentication" time="0.26"/>
	<testcase name="testTrustedAuthentication" time="0.11"/>
	<testcase name="testTrustedExist" time="0.09"/>
	<testcase name="testTrustedSession" time="0.081"/>
	<testcase name="testActionMgrSerialization" time="2.363"/>
	<testcase name="testSessionSerialization" time="0.09"/>
...
</testsuite>

The solution could be to add the test package & class information in the XML 
formatter output, and to change the JunitReport task...

Or an other solution might be to have the option to fork a VM just once, for 
all the tests. This would allows to use the JUnitReport the way it works now, 
and solve the performance problem.

I would like to have your opinion about this problem. If you have suggestions, 
I could try to make a patch with them.

Thank you
Fabrice

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message