Plugin installations:
I didn’t have any headaches. I consider plugin installation as advantage of Eclipse, because Eclipse can restart itself afterwards.

Unit-testing:
Put your caret on the test method declaration, then press standard F11 in Eclipse. Anywhere else in class it will run the Test Case. Whether inside the method should run that method only or whole class is just a matter of habit.

‘Actions on commit’ in IDEA can be emulated by ‘Actions on save’ in Eclipse.

Tip of the day:
I rarely have to wait in Eclipse so long while not being able to continue in my work. In Eclipse almost every process can and do work in background. The only bad one I can come up with is the Update process of Eclipse.

You are right. I always perceived that camel-search would not work, because the search type is taking the capitals as lowercase search pattern too. For instance: typing MAT would both match
MultipleAnnoyanceTest and Matchpoint.

The IntelliJ search has another nice benefit: You can quickly exclude non-project types (which is default). In eclipse as far as I know, this is only possible with defining workingsets and package filters. Most often when I use type search I look for types in working project only.

About the JUnit thing, you can execute single tests by Outline and JUnit view, but I think it goes much nicer if you got a handy shortcut inside the editor.

If you run the test method from the Outline view, it will only run the one test.