Static Imports in Eclipse with Quick Fix
Join the DZone community and get the full member experience.Join For Free
Not sure what is so complicated about static imports that eclipse can still not get support for them straight, even in 3.5M7. Using hamcrest and even JUnit 4 is made much more unpleasant than it should be by the fact that getting these things into tests is such a nuisance. For instance, I do a simple assertThat statement, then use equalTo or closeTo, and I would like to be able to do just Apple-Shift-O (Organize Imports) and get all those things put in. That doesn‘t work. Next best thing would be to just go to each instance and do Apple-1. That does work once in a while, but not most of the time.
Today, I did some searches and found the suggestion of adding the types (e.g. org.junit.Assert) to the favorites tab or Content Assist.
What this does, is it makes it possible for you to get the suggestion inline and if you take it, it will add the import,
but Organize Imports still doesn‘t work:
The other solution, of course, would be to just add the imports to the template that the junit plugin is using (should be a super simple, configurable choice, but alas, it is not).
So this is better than not having the content assist working, but still not optimal.
Opinions expressed by DZone contributors are their own.