Improvingworks Infinitest

Dominik Steiner [dominik.j.steiner@googlemail.com]

thanks for your interest in my opinion about infinitest. I have been quite happy with it and it certainly has helped to improve the quality of my software development:

What I liked:

• I was surprised to see the integration in eclipse to be seemless, to the point were i first even was surprised to see errors where i couldn't see any. (at least from a syntax point of view which i was used to)
• clicking on the error in the problems view and bringing me directly to the error has proven an efficient way of getting to the point
• the support has proved fast and has resolved my issues with the product

What i found difficult:

• the time from instalation to actually being able to run the first tests with infinitest proved painfull. I was surprised to hear that all the projects in the workspace had to be error free in order for the tests to run. I would find it more intuitive if only the project under test or at least a selected working set would be the target for the tests.
• also i had to completely move my projects to another workspace in order to actually not crash my eclipse after installation

What i would like to see:

• I have seen now several times that tests mark errors on spots where they don't occur, this is especially true when using nested anonymous classes. I would like to see that fixed in a future release
• Also it would be great to have the stacktraces of the failed tests somewhere on a quick glance (right now if i'm not sure about why a test and how it failed i run the test with junit directly)

I hope that you further improve this useful product, thanks

Dominik