Blog

Eclipse Tip: Keep static imports for JUnit 4

12 Oct, 2008

If you are using Eclipse to write your JUnit 4 tests you might have noticed that when you organize the imports, the line

import static org.junit.Assert.*;

at the top of your JUnit 4 classes is replaced by stuff like:

import static org.junit.Assert.assertTrue;
import static org.junit.Assert.assertNotNull;


While your code still compiles and runs OK, this forces you to add another specific static import every time you want to use another static assert method like assertEquals.
Luckily this can be fixed by going to Windows/Preferences…, going to the Java/Code Style/Organize Imports tab and then entering 1 where it says “Number of static imports needed for .*” and then clicking the OK button.
Hope this helps!

guest
9 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
p3t0r
13 years ago

Also, add ‘org.junit.Assert’ or any of your static helper methods to your ‘favorites’ (preferences, search for favorites). This makes working with static imports much easier.

Martin Tilma
13 years ago

I just wrote on the same issue (http://www.func.nl/community/knowledgebase/eclipse-and-static-imports) but the solution differences a bit.

p3t0r
13 years ago

@Martin Tilma … that is exactly what I said in my first comment… but thanks for elaborating 😉

Ron
Ron
13 years ago

Great tip!
cheers, Ron

trackback

[…] idea taken from http://blog.xebia.com/2008/10/12/eclipse-tip-keep-static-imports-for-junit-4/ Tagged as: Eclipse, JUnit 4 Leave a comment Comments (0) Trackbacks (0) ( subscribe to […]

Janosch
Janosch
11 years ago

Thanks!
Had been annoying me for a long while, and this is now over :-).

Strangeoptics
10 years ago

Exactly what I was searching for.
I am Writing a Posting about Eclipse shortcuts and the drawback of organise imports.
Best Of Short Cuts For Eclipse
Thanks.

Shalom Shachne
Shalom Shachne
10 years ago

Thanks for posting all the tips. Very big help, and increased my productivity right away!

Explore related posts