Strategies for separating unit and integration tests, using Maven, Eclipse / IDEA, cobertura

What I have

• Maven2
• Eclipse/IntelliJ IDEA
• Fast tests (unit tests)
• Slow tests (integration tests)
• Test coverage maven plugin (Cobertura)

I wish to

• run my fast tests (unit tests) from my IDE
• run my slow test (integration tests) from my IDE and maven
• run them all before committing code.
• create test coverage reports combining unit and integration tests
• create test coverage reports from unit tests only

The only good branch is a dead branch

edit: so kill them fast :)

Maven Dependency Hell

Yeah, I knew you’ve felt the same some times! Some developers are suddenly experiencing local problems, while others doesn’t, even as they’re having the same code base. The experienced developer thinks “classpath problem!”, almost as a reflex! And they’re always right, it’s yet another a damned jar that’s been automagically downloaded by maven from an other automagically loaded jar dependency. Anyway, that’s how it feels like for me. It’s often time-consuming to discover the reason, even more time-consuming if “classpath-problem” isn’t your first thought (god, no)! If not, say bye bye to productivity for that day. Been there, done that!

How to avoid it? Eliminate the automagic dependencies. Exclude these dependencies and explicitly define all used dependencies.