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 249170 - JUnit output window often doesn't show the results during the test and also when it's finished
Summary: JUnit output window often doesn't show the results during the test and also w...
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 8.0.2
Hardware: PC Windows 7
: P1 normal (vote)
Assignee: Theofanis Oikonomou
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-06 15:40 UTC by netbeansuzr
Modified: 2014-12-20 12:52 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 netbeansuzr 2014-12-06 15:40:11 UTC 
When running a single test class or a suite with 2 classes, the progress bar shows fine, but the methods being run and the total tests run and the total time taken are not shown when the test finishes most of the time (once in a while they are shown, but rarely).

Often times the tests start showing up while the tests are running in the window, and you can expand it and see 1 test showing up, but as more tests run, they never show up in the JUnit output window and then when all the tests finish, all the existing output disappears and the only thing visible in the JUnit window is the green progress bar with "100%" on it.

I'm using the latest version of NetBeans, tried upgrading to jdk1.8.0_25 from jdk1.8.0_05 for both the NetBeans IDE and my Java projects, then deleted the cache and it still fails.
Comment 1 Theofanis Oikonomou 2014-12-18 14:56:05 UTC 
I am sorry but I cannot reproduce. Can you reopen describing what steps I need to follow? Also please attach a sample project or testcase where this behavior is shown. Is it only present in ant or in maven project? Log file and a screenshot will also help. Thank you for reporting.
Comment 2 netbeansuzr 2014-12-20 02:47:14 UTC 
It's only present in an ant project, I don't use maven.  Hope that helps.
Comment 3 netbeansuzr 2014-12-20 12:52:26 UTC 
This might be related to or made more likely to happen when running unit tests in one class or multiple unit tests in parallel.