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 51977 - Test randomly created under source root
Summary: Test randomly created under source root
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: junit-issues@java
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2004-12-01 15:37 UTC by _ rkubacki
Modified: 2006-03-24 12:46 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 _ rkubacki 2004-12-01 15:37:41 UTC 
I've experienced this randomly with some builds of
NB4.1 last time with build from Nov 30.

Create a simple project with couple of classes
(interface, package private implementation and
class with factory method and private
constructor). Then I tried to create tests for
various classes and sometimes I get the generated
class created under src folder rather than under
test/src.
Comment 1 _ rkubacki 2004-12-01 15:38:30 UTC 
BTW: I run on JDK5.0 and this happened to me on Solaris as well as on
Linux.
Comment 2 Marian Petras 2004-12-07 13:38:30 UTC 
Accepted, although I have not noticed the described behaviour.

Please leave a note the next time it happens so that I know whether it
got fixed somehow or it remains to be a problem.
Comment 3 Marian Petras 2005-01-24 10:26:11 UTC 
Have you encountered the bug since you filed this bug?
Comment 4 _ rkubacki 2005-01-24 10:46:46 UTC 
I did not (maybe because I did not used this function too often since
I filled the bug).
Comment 5 Marian Petras 2005-01-24 10:51:13 UTC 
I have created many test classes since this bug was reported. I have
used both the Create Tests dialog and the JUnit wizards. I have not
encountered this bug.

The bug was probably caused by a bug in another module (probably
"projects"). Since the bug is not reproducible now, it seems the bug
has been fixed since then. Marking as FIXED.
Comment 6 Max Sauer 2006-03-24 12:46:33 UTC 
This is not reproducible both inside nb 5.0fcs and nb6.0 dev 200603141900.
(FIXED && TM==4.1) => CLOSED