Bug 21431 - JUnit wizard should import tested class when testing class isn't in the same package [JUnit]
Summary: JUnit wizard should import tested class when testing class isn't in the same ...
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2002-07-10 04:25 EDT by Giovanni Corriga CLA
Modified: 2009-08-30 02:14 EDT (History)
2 users (show)

See Also:

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 Giovanni Corriga CLA 2002-07-10 04:25:49 EDT 
When I'm working on a package mypackage, I usually put all my JUnit test cases
in package mypackage.test. When I use the wizard to create MyClassTest (where
MyClass is the class I'm testing), I change in the dialog the package where
MyClassTest belongs from mypackage to mypackage.test.
The wizard should add 'import mypackage.MyClass;' to the generated code, instead
of doing nothing like it does now.
Comment 1 Dirk Baeumer CLA 2003-02-05 14:55:26 EST 
Still exists under M5 2.1.

Given the current schedule we have to postpone > 2.1
Comment 2 Sebastian Davids CLA 2003-05-07 11:09:45 EDT 
The generated class (mypackage.test.MyClassTest) does not have a reference to
the tested class (mypackage.MyClass) yet.

If the compiler setting "Unused imports" is set to Warning (default) or Error
the generated code would produce an Warning/Error.

Generated code should not contain "Warnings/Errors".

Once you use the class ... one Ctrl+Space and the requested import is there ,)
Comment 3 Denis Roy CLA 2009-08-30 02:14:36 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.