Eclipse Community Forums: Java Development Tools (JDT)

Home » Language IDEs » Java Development Tools (JDT) » Best Practices re JUnit

Best Practices re JUnit [message #515394]

Thu, 18 February 2010 11:32

Eclipse User

I would like some advice on the best way to organize my JUnit test classes in Eclipse 3.5.1. Should a given JUnit test class be in the same package as the class that it is testing? Or should it be in a different package within the same project? Should it be in the same project as the one being tested or perhaps in a separate project?

I'm not having any trouble writing and executing my JUnit tests; I'm just not sure about the best way to organize them within Eclipse.

--
Rhino

Re: Best Practices re JUnit [message #515547 is a reply to message #515394]

Fri, 19 February 2010 05:42

Eclipse User

Reinhardt Christiansen wrote:
> I would like some advice on the best way to organize my JUnit test
> classes in Eclipse 3.5.1. Should a given JUnit test class be in the
> same package as the class that it is testing? Or should it be in a
> different package within the same project? Should it be in the same
> project as the one being tested or perhaps in a separate project?
In Eclipse we use separate projects because it gives a clear separation
and makes building the (runtime) product easier.

Dani
>
> I'm not having any trouble writing and executing my JUnit tests; I'm
> just not sure about the best way to organize them within Eclipse.
>
> --
> Rhino

Re: Best Practices re JUnit [message #515593 is a reply to message #515547]

Fri, 19 February 2010 08:50

Eclipse User

Thank you for that information, Dani.

What do you do about package names for test cases? For example, if the package being tested is com.foo.baz, does the package for the test cases have the same name or does it get a different name, something like com.foo.baz.test?

--
Rhino

Re: Best Practices re JUnit [message #515601 is a reply to message #515593]

Fri, 19 February 2010 08:52

Eclipse User

Reinhardt Christiansen wrote:
> Thank you for that information, Dani.
>
> What do you do about package names for test cases? For example, if the
> package being tested is com.foo.baz, does the package for the test
> cases have the same name or does it get a different name, something
> like com.foo.baz.test?
See http://wiki.eclipse.org/Naming_Conventions

Dani
>
> --
> Rhino

Re: Best Practices re JUnit [message #515605 is a reply to message #515601]

Fri, 19 February 2010 09:16

Eclipse User

I see! So my test package would be com.foo.tests.baz and it would be in its own project.

Thank you very much, Dani!

--
Rhino

Previous Topic:	How to highlight reconciliation error in the texteditor
Next Topic:	Viewing MANIFEST files for JARs in my build path

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 20 09:38:32 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter