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 172750 - Using System.out makes suite aborting
Summary: Using System.out makes suite aborting
Status: RESOLVED DUPLICATE of bug 167429
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Yulia Novozhilova
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-22 10:57 UTC by fgeorges
Modified: 2011-08-09 11:34 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 fgeorges 2009-09-22 10:57:18 UTC 
Hi,

  I am using NetBeans 6.7.  When I run a test suite using JUnit
4, its final state is ABORTED while the test cases are flaged as
passed.  Actually, not all cases are run, the suite stops after
a few ones.

  The SUT does use an OutputStream, and I use System.out for the
tests.  It seems to be relevant as if I use System.err instead,
everything runs fine, as well as if I use a no-op OutputStream
(an "empty implementation".)

  I do not know for sure this is a bug of the JUnit support of
NetBeans, but I don't know where and how I could find more
information about the failure...  Is there any logging that
could be enabled, in order to provide more information?

  Kind regards,

-- 
Florent Georges
http://www.fgeorges.org/
Comment 1 Victor Vasilyev 2009-09-25 18:09:21 UTC 
Florent,

I can't reproduce this bug.
Could you please, provide a small sample project where such bug could be reproduced.

---
Victor Vasilyev
Comment 2 dmitri616 2009-10-08 14:03:34 UTC 
Seems to be related to 167429
Comment 3 jader2000 2011-03-01 13:37:39 UTC 
In version 6.9.1 bug still exists. Any intense use (few hundreds output lines) of system.out.println cause it.
Comment 4 Yulia Novozhilova 2011-08-09 11:34:31 UTC 

*** This bug has been marked as a duplicate of bug 167429 ***