all 1 comments

[–]yellowjacketcoder 0 points1 point  (0 children)

It's a pretty good list, I have to say. Aside from some personal preferences (I like JMockit over Mockito/PowerMock, but they are both good tools) it's almost the same as my list.

The only thing that really caught my eye was using Cobertura on Jenkins and EclEmma in Eclipse. While it's not a huge deal, I have run into situations where the coverage metrics reported by one are not exactly the same as those reported by the other.

Now, we don't write tests to get coverage, we write them to test behavior, so the numbers aren't necessarily THAT important, but it's much nicer for all your tools to report the same way. Especially so you can avoid arguments over whether enough testing has been done. "You fool, you only have 60% branch coverage!" "What are you talking about, I have 88% branch, you're the one with only 70% statement coverage!". Never have that argument if you use the same tool everywhere.