<p>I've used the <a href="http://groups.csail.mit.edu/pag/continuoustesting/" rel="noreferrer">MIT Continuous testing</a> 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. </p>

<p>Does anyone have a good replacement? Free, naturally, is preferred. </p>

[{'answer_id': 77260, 'author': 'Bradley Harris', 'author_id': 10503, 'author_profile': 'https://Stackoverflow.com/users/10503', 'pm_score': 2, 'selected': False, 'text': '<p>There is a list in this Ben Rady article at Object Mentor: <a href="http://blog.objectmentor.com/articles/2007/09/20/continuous-testing-explained" rel="nofollow noreferrer">Continuous Testing Explained</a>.  Unfortunately the only Eclipse tool appears to be <a href="http://ct-eclipse.tigris.org/" rel="nofollow noreferrer">CT-Eclipse</a> which is not currently maintained either.</p>\n\n<p>There is also <a href="http://swing1979.googlepages.com/fireworks" rel="nofollow noreferrer">Fireworks</a> for IntelliJ and <a href="http://www.infinitest.org/" rel="nofollow noreferrer">Infinitest</a> which is not IDE specific but also has some IntelliJ integration.</p>\n'}, {'answer_id': 88380, 'author': 'Oisin Hurley', 'author_id': 16912, 'author_profile': 'https://Stackoverflow.com/users/16912', 'pm_score': 2, 'selected': False, 'text': '<p>My experience is that continuous testing within the IDE can become unwieldy and distracting, so I prefer to use something like <a href="http://cruisecontrol.sourceforge.net/" rel="nofollow noreferrer">CruiseControl</a> to do this kind of testing. One tool I have found very useful is <a href="http://www.eclemma.org/" rel="nofollow noreferrer">EclEmma</a>, 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.</p>\n'}, {'answer_id': 161228, 'author': 's3v1', 'author_id': 17554, 'author_profile': 'https://Stackoverflow.com/users/17554', 'pm_score': 1, 'selected': False, 'text': "<p>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.</p>\n"}, {'answer_id': 1479467, 'author': 'awied', 'author_id': 13812, 'author_profile': 'https://Stackoverflow.com/users/13812', 'pm_score': 4, 'selected': True, 'text': '<p>I found that <a href="http://infinitest.github.com/" rel="noreferrer">Infinitest</a> now has an Eclipse plugin that seems to work pretty well. </p>\n'}, {'answer_id': 2986441, 'author': 'Mo Mo', 'author_id': 359953, 'author_profile': 'https://Stackoverflow.com/users/359953', 'pm_score': 2, 'selected': False, 'text': '<p>Infinitest decides what tests it wants to run. Often it runs the wrong ones. Green bar sometimes good, sometimes meaningless.</p>\n'}, {'answer_id': 6425104, 'author': 'Bananeweizen', 'author_id': 44089, 'author_profile': 'https://Stackoverflow.com/users/44089', 'pm_score': 1, 'selected': False, 'text': '<p>I also use Infinitest (and voted for one of its answers), but I wanted to add another approach, which <strong>relies on the build server</strong>. Whenever you want to implement something, create a branch in your VCS, do your changes, commit to your branch. If you have a build server configured, which runs unit tests on every checkin, your unit tests are then run on the build server without actually having polluted the trunk (or HEAD, whatever you call it) and without you waiting for the test run to finish.</p>\n\n<p>I admit that this is not really continuous unit testing in the sense you asked the question, but for large projects or large test suites even a "normal" continuous test runner may slow you down way to much.</p>\n\n<p>For small projects I also recommend Infinitest or CT Eclipse.</p>\n'}]
['https://Stackoverflow.com/questions/77090', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/13812/']