Problems with Assertions in JUnit tests using Eclipse (CodingClues)

Jun
30

Problems with Assertions in JUnit tests using Eclipse

You are wondering why your JUnit tests run very fine when you launch them using Eclipse, whereas they all break down when building your project with a build system like Ant or Maven?

Well, thats probably because you are using assert statements and Eclipse per default is not configured to evaluate them.

To solve this problem, simpy go to Run -> Run… -> Arguments, and in the box labeled VM arguments:, enter either -enableassertions or just -ea.

That’s it!

Are you interested in reading more from CodingClues?
Then subscribe to new postings via RSS or via E-Mail.

Viewing 2 Comments

deepakp9 01/20/2009 03:35 PM 1 point
Please login to rate.

Do you already have an account? Log in and claim this comment.

Eclipse v. 3.1comes with JUnit built into the Workbench. Eclipse allows you to quickly create test case classes and test suite classes to write your test code in. With Eclipse, Test Driven Development (TDD), becomes very easy to organize and implement.

http://add-blogbanner.blogspot...

reply edit reblog flag

0 /people/deepakp9/ /people/deepakp9/following/

guruz 06/30/2008 05:04 PM 1 point
Please login to rate.

Do you already have an account? Log in and claim this comment.

Another thing to keep in mind: maven will run each test in its own JVM, eclipse will run them in the same JVM. So do your cleanup work in the unit tests so you leave no static data somewhere that influences your tests.

reply edit reblog flag

1 /people/guruz/ /people/guruz/following/ http://blog.guruz.de/