Include Unit tests in the same package as the source code in Java

Question

I'm getting back into Java after a long stint in the Ruby world and I've got a question about JUnit tests and the source I'm testing.

If I've got a package of graphics code for my company, lets call it com.example.graphics, should I include my tests in that package too or should they be included in a seperate package, like com.example.graphics.test?

See also http://stackoverflow.com/questions/440786/junit-java-testing-non-public-methods — Raedwald, Jun 30 '14 at 22:53

score 38 · Accepted Answer · answered May 24 '10 at 16:32

38

In the same java package is fine. It's actually necessary if you need to access package-private classes, methods, or fields. However, the source should be logically separate:

src/main/com/example/graphics
src/test/com/example/graphics

answered May 24 '10 at 16:32

Brett Kail

33,148
2
86
88

1

+1, as suggested by the Maven Java Archetype standard directory layout – Ramiro González Maciel May 24 '10 at 16:34
I suggest opening a new question rather than commenting on an 8 year old answer. I suggest focusing on what specific problem you're having and what you've done to try to solve it. – Brett Kail Jan 22 '19 at 02:46

score 1 · Answer 2 · answered May 24 '10 at 16:36

1

If you do not need to access private classes it is actually a question of flavor.

I sometimes even tend to create an additional test-project referenced to the product-project. Therefore, product and test are clearly seperated.

answered May 24 '10 at 16:36

Philipp Andre

917
2
11
17

score 1 · Answer 3 · answered May 24 '10 at 16:52

I personally keep all my tests in the same package, but in the test tree of Maven(which I always use for Java projects). Consider using Maven for your builds as well - it saves a lot of work on your part. It enforces a similar structure to what bkail mentions, but gives you much more than a standardized project folder layout - project lifecycle(clean, compile, package, test), plugins, etc .

score 0 · Answer 4 · answered Jul 24 '10 at 19:29

0

Putting tests in a separate package does tend to avoid the problem of accidentally having some method or class at package-scope that you intended clients to use.

answered Jul 24 '10 at 19:29

soru

5,362
24
30

Include Unit tests in the same package as the source code in Java

4 Answers4