NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ
for more details.
In a big code porting project recently I had to move a number of unit tests from one class over to another. I didn't give it a second thought beyond that until it came to running the build. Compilation was successful, however JUnit execution failed on the tests I moved. Odd. At first I thought maybe I accidentally changed some code, but no, all the code was the same. Then I realised what the problem was.
The class that I moved these tests from was written for JUnit 4.x
and used the @Test
annotation. However the class that originally had these tests was written for JUnit 3.x
and was extending the TestCase
class and no annotations.
This meant that my perfectly legitimate test case like that looked like this...
...would always cause my build to fail when executed inside a test case designed for use with JUnit 3.x
The solution was of course not to mix the two approaches. In my case, I removed the 'extends TestCase'
from the class and added @Test
annotations to every other test case inside it. Once that was done, all my tests were passing again.
I've come across this article while debugging the issue above, it's worth a read when migrating from JUnit 3.x
- Junit 3 vs Junit 4 Comparison
A quick disclaimer...
Although I put in a great effort into researching all the topics I cover, mistakes can happen.
If you spot something out of place, please do let me know.
All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle).
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...