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.
Weird messages are shown inside Junit test results window ("Information about passed tests is not displayed", altough passed tests are displayed), and the button that switches between passed/all test gets disabled during test execution. See attached screenshot. Following message is shown inside console, while the tests are executed: WARNING [null]: Do not call reset() on the error io, only on the output IO. Reset on the error io does nothing. It happens only when the project contains passing tests. Steps to reproduce: ------------------- 1) Create a j2se project 2) Create a test for Main.java (Ctrl-shift-u, confirm) 3) Create a new java class 4) Create a method inside 5) Create a test for this class, which should pass 6) Test project (Alt-F6) -------- NetBeans IDE Dev (Build 200605281800) 1.6.0-beta2; Java HotSpot(TM) Client VM 1.6.0-beta2-b84 SunOS version 5.10 running on sparc en (nb); ISO646-US
Created attachment 30650 [details] screenshot
I have reproduced it on Linux. It seems to be random, which is strange.
So this is random on Windows and Linux but 100% reproducible on Solaris.
We have realized that this issue is very difficult to reproduce on most maschines. P2->P3.
I've reproduced this with 5.5beta2. ---------- Product Version = NetBeans 5.5 Dev (Build 200607110200) Operating System = SunOS version 5.10 running on sparcv9 Java; VM; Vendor; Home = 1.6.0-rc; Java HotSpot(TM) 64-Bit Server VM 1.6.0-rc-b90; Sun Microsystems Inc.; /usr/jdk1.6.0/jre System Locale; Encoding = en (nb); ISO646-US
*** Issue 86880 has been marked as a duplicate of this issue. ***
This should not happen since bug #96416 ("Information about passed tests is not available sometimes") had been fixed. I have not seen such a bug since then. The first NetBeans milestone (semi-version) with this bug fixed is NetBeans 6.0 M8. I am marking this bug as FIXED. Feel free to reopen it if you ever reproduce it again.
*** Bug 177170 has been marked as a duplicate of this bug. ***