The new version of the plug-in has been released and is ready to use. Changes have been made to allow continuous testing on plug-in development projects. Updates for Version 1.1.2
***In order to use JUnit Plug-in Tests*** A reminder that in order for Eclipse to run JUnit Plug-in Tests, the plug-in must have org.junit listed in its dependencies.
***Filter/Prioritizer Developers*** One point of interest for anyone developing their own filter or prioritizer extensions is that the interfaces have been moved. The filter interface is now located at org.eclipse.jdt.junit.runner.ITestFilter, and the prioritizer is now at org.eclipse.jdt.junit.runner.ITestPrioritizer.
On August 6th, 2004, a new release of the plug-in was released. The new release adds to the functionality of the plug-in and adds many new features to the JUnit plug-in for Eclipse.
We would like to hear your thoughts on the new features. We are excited to see the prioritizers and filters that you can create and use with the new release.
NOTE: The new version of the continuous testing feature comes with replacement plug-ins for Eclipse's JUnit support. If you wish to go back to using the original JUnit plug-ins, you must uninstall the continuous testing feature; simply disabling it will also disable the default JUnit functionality.
There is also now a separate bugzilla repository just for the plug-in, at http://pag.csail.mit.edu/zilla. Please make further enhancement requests and bug reports there. Share and Enjoy.
I have now attached v1.0.1, which works with both M6 and M7. Further bug reports and feature requests are appreciated.
Attached is a plug-in that implements continuous testing, as described below. A user study with students has shown that continuous testing has measurable productivity benefits in certain situations--I think it could be a very useful part of the standard Eclipse toolset. It currently is only tested against Eclipse 3.0 M6.
Continuous testing builds on the automated developer support in Eclipse to make it even easier to keep your Java code well-tested, if you have a JUnit test suite. With continuous testing enabled, as you edit your code, Eclipse runs your tests quietly in the background, and notifies you if any of them fail or cause errors. It is most useful in situations where you would already have a test suite while you are changing code: when performing maintenance, refactoring, or using test-first development.
Continuous testing builds on the following features of Eclipse:
Continuous testing was first developed by David Saff at MIT as part of his PhD research. Let me know if it sounds useful to have it as part of the base distribution, and what next steps would be required to begin getting it to the state where that could happen.