Improvingworks Infinitest

Anders Sveen [anders@f12.no]

Over all I'm really liking the product, but it could be more spot on. The main things that's not working too well:
• Figuring which tests that needs a re-run
• When to run tests
Now, the first one is really connected to Spring etc. So when I change config files in Spring the tests are not re-run. I completely understand if this is stuff that's hard to manage, but still it would be a killer feature.

The second issue might be connected to the actual error message, but when I know something is wrong I fire up the tests in the normal JUnit runner in Eclipse. This is basically because it's hard to get enough information out from the error in the problems view. I also have asserts in classes used by the tests, so double clicking on the error takes me to the "resusable" method, while usually I would like to go to the line that failed in the test. So when I then run the test in Eclipse, sometimes the Infinitest runner is running at the same time. Because I'm launching a web-server in a static context, this can actually sometimes interfere with eachother. So an option to pause the tests while JUnit is running in standard would probably come in handy.

Hope that's clear enough, let me know if something is unclear.

Thanks,
Anders,b