A neat little Eclipse plugin I’m playing with at the moment is the Continuous Testing Plugin for Eclipse The basic purpose of this plugin is to run your tests (or a selected subset) as part of the build cycle in Eclipse.
This is having some interesting behaviour for me. Firstly, I’m not having to manually push the button. I just save, and Eclipse tells me if the tests break. Test failures show up as problems (the same way compile errors do), which means that they become very visible for me. I’m also strongly motivated to keep (at least a subset!) of tests really fast, which is a Good Thing(tm).
The feedback loop is being kept really really tight. I try something, save it, see if it works, move on. It also makes it easy to see what isn’t tested: if you’re changing something and a test doesn’t break, then it wasn’t tested. 🙂
It’s also smart enough to be able to re-order how tests are run. In particular, it can prioritise most recently failing tests, most frequently failing tests, or the fastest running tests (for quick feedback). I’ve got it set on the first setting.
While I wouldn’t want to use this on a slow computer, it seems okay on my home PC. About the only real quirk is that the current version outputs stuff to the Console, so you have to turn off the “auto-switch to console” setting (Window -> Preferences -> Run/Debug -> Console, then the two “Show when program writes…” check boxes).
One thought on “Automated Test Running”
Automated Test Running
sounds like a great idea in theory. With so many processes already
running on my machine (tomcat, MySQL, JBoss) …