#1 New test packages created in the wrong directory

[Michael Hirsch]

If a package does not already exist in my test directory, it
usually gets created in the wrong place. To be more specific, I
use src/$PACKAGE$/$CLASS and test/$PACKAGE$/$CLASS$Test
as my pattern for matching a class and the test. Suppose I have
a class a.b.c.ClassName but there are no tests yet for any
classes in the a.b or a.b.c packages. The the a directory will not
have any b subdir.

When I create a test for ClassName I will get a ClassNameTest
class which specifies that it is in the a.b.c package, but it will
show up in some other package like a.d.ClassNameTest.

This is quite reproducible. It has been around for a while. I am
currently using idea 3.0.4 with UnitTest701. I find it under both
Linux and Windows.

[Paul S. Hawke]

Logged In: YES
user_id=4473

Tests for our project live in a single big "code bucket"
called simply "test" at the top level of the package
hierachy. If I attempt to specify an absolute path (with a
'/' at the start) the plugin assumes the package to be a
sub-package of my current class, as though it were a
relative reference (ie, like a directory reference without
the leading '/'). As it stands I am unable to use the
plugin to enhance the maintainance of our test-coverage in
the project I'm on.