{"id":29163,"date":"2016-07-20T15:00:14","date_gmt":"2016-07-20T12:00:14","guid":{"rendered":"http:\/\/examples.javacodegeeks.com\/?p=29163"},"modified":"2019-03-21T11:59:29","modified_gmt":"2019-03-21T09:59:29","slug":"junit-unrooted-tests","status":"publish","type":"post","link":"https:\/\/examples.javacodegeeks.com\/java-development\/core-java\/junit\/junit-unrooted-tests\/","title":{"rendered":"Junit Unrooted Tests"},"content":{"rendered":"

1. Introduction<\/h2>\n

One common mistake that developers make in creating JUnit is the version mismatch. Projects seems to be now keen on creating Junit test cases using the more advance annotation based (JUnit 4) rather than the older way (Extending TestCase class) of doing it.<\/p>\n

A common error or issue is when a developer loads\/imports a JUnit 4 on the project but creates a Junit source using the JUnit 3 approach (extends test case with TestCase class). This will clearly result in a configuration issue such as missing dependency\/library or incompatible library versions. JUnit libraries were made to be backward compatible but it’s always safe to stick with a specific one to avoid further issues.<\/p>\n

In our example below, we will be tackling one of the few issues that a developer may encounter during this unwanted crisis. It shows a typical junit scenario configured to comply with the JUnit4 standards.<\/p>\n

JUnitSampleUnRootedTest.java<\/em><\/span><\/p>\n

package com.junit.unrooted.test.sample;\n\nimport static org.junit.Assert.assertTrue;\n\nimport org.junit.Before;\nimport org.junit.Test;\nimport org.junit.runner.RunWith;\nimport org.junit.runners.BlockJUnit4ClassRunner;\n\nimport junit.framework.TestCase;\n\n@RunWith(BlockJUnit4ClassRunner.class)\npublic class JUnitSampleUnRootedTest {\n\t\n\tint totalNumberOfApplicants = 0;\n\tint totalNumberOfAcceptableApplicants = 10;\n\t\n\t@Test\n\tpublic void testAssertions() {\n\t\tassertTrue((this.totalNumberOfApplicants != this.totalNumberOfAcceptableApplicants));\n\t}\n\n\t\n\t@Test\n\tpublic void testAssertTrueWithMessage(){\n\t\tassertTrue(\"Is total number of applicants acceptable?\",(this.totalNumberOfApplicants != this.totalNumberOfAcceptableApplicants));\n\t}\n}\n<\/pre>\n
The issue is, that the developer is using JUnit 3 library as oppose to Junit4. This resulted to the following error after trying to run the unit test case.
 
<\/div> <\/div><\/p>\n
\"\"<\/a>
Figure 1.0 Unrooted test case<\/figcaption><\/figure><\/p>\n
2. Solution<\/h2>\n
The solution is basically just to use the correct library. This will let JUnit get the correct implementation and thus avoid having a JUnit Test that’s unrooted. To load the library in eclipse, simple either use the implicit features (by adding libraries to the project) or via maven.[ulp id=’ODQaBEw1BIbHApZq’]<\/p>\n
Project Libraries<\/h3>\n
Make sure to import the JUnit library on your eclipse properly. Do a few refresh of the workspace and build projects to ensure that it picks up.<\/p>\n
\"2.0<\/a>
2.0 JUnit Library via eclipse<\/figcaption><\/figure><\/p>\n
Maven<\/h3>\n
Make sure to update the project settings after putting the dependency on your pom.xml. This will ensure that eclipse will pick it up and import it on your project.<\/p>\n
<dependency>\n    <groupId>junit<\/groupId>\n    <artifactId>junit<\/artifactId>\n    <version>4.12<\/version>\n<\/dependency>\n<\/pre>\n
Here are useful links\/reference to forums that would give in depth information about this:<\/p>\n