This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 171279 - Test case times listed as 0.0s until suite completes
Summary: Test case times listed as 0.0s until suite completes
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Theofanis Oikonomou
URL:
Keywords:
: 185518 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-09-01 18:30 UTC by Jesse Glick
Modified: 2016-07-07 07:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2009-09-01 18:30:23 UTC 
Current dev builds (broken for a while). At least when running JUnit 3.x tests from Ant, as test case nodes are
displayed beneath the suite node in the Test Results window, they are listed as e.g.

  testAreAttributesFine passed (0.0s)

Only when the suite completes are the actual times shown:

  testAreAttributesFine passed (7.515s)
Comment 1 Victor Vasilyev 2009-11-16 08:18:50 UTC 
It is valid issue for NB6.8

The JUnit module of the NetBeans completely relies on the Ant's junit task for execution of the tests, and the org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner is used. See http://www.docjar.com/html/api/org/apache/tools/ant/taskdefs/optional/junit/JUnitTestRunner.java.html

Seems the JUnit module can catch the message in the log like this: 

junit.framework.TestListener: tests to run: {suite.countTestCases()}

and each next log message like this:

junit.framework.TestListener: startTest({testName})
junit.framework.TestListener: endTest({testName})

where {...} some values.

Processing these messages and values might give us a chance to visualize progress of the test process.
Comment 2 Jesse Glick 2011-04-21 17:39:09 UTC 
*** Bug 185518 has been marked as a duplicate of this bug. ***
Comment 3 Martin Balin 2016-07-07 07:17:34 UTC 
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss