views:

446

answers:

5

I've used the MIT Continuous testing plugin in the past, but it has long since passed out of date and is no longer compatible with anything approaching a modern release of Eclipse.

Does anyone have a good replacement? Free, naturally, is preferred.

+2  A: 

There is a list in this Ben Rady article at Object Mentor: Continuous Testing Explained. Unfortunately the only Eclipse tool appears to be CT-Eclipse which is not currently maintained either.

There is also Fireworks for IntelliJ and Infinitest which is not IDE specific but also has some IntelliJ integration.

Bradley Harris
CT-Eclipse is not (from what I can tell) in active development now. Fireworks is not for Eclipse. Inifinitest works _okay_, but crashes on large projects and does not integrate with Eclipse. Thanks for the info, though.
awied
+2  A: 

My experience is that continuous testing within the IDE can become unwieldy and distracting, so I prefer to use something like CruiseControl to do this kind of testing. One tool I have found very useful is EclEmma, which gives you a very fast coverage turnaround for your units, helping you to decide when you have finished testing a particular area of the code.

Oisin Hurley
Although pointing to traditional Continuous Integration tools is certainly nice, continuous feedback in the IDE is still more frequent by at least 1 order of magnitude (I'd even say 2), so I don't feel this is really answering the question.
Thomas Dufour
+1  A: 

I've had good experience with infinitest on a small and simple project. I've not run into any issues with it and find it fast and helpful.

Sebastian
Just an update. Infinitest 5.x is still running great and running fine in current versions of Eclipse and Intellij
Sebastian
+2  A: 

I found that Infinitest now has an eclipse plugin that seems to work pretty well.

awied
+1  A: 

Infinitest decides what tests it wants to run. Often it runs the wrong ones. Green bar sometimes good, sometimes meaningless.

Mo Mo
I've suffered more from meaningless red bars from infinitest actually. Also, as I tend to save every couple of lines at most, infinitest ended up always running (and not often displaying results). As a result I've dropped it even though I'm convinced by continuous testing in principle...
Thomas Dufour