Improvingworks Infinitest

Alex Bepple [alex.bepple@it-agile.de]

Thank you for following up.

I have only used Infinitest for educational purposes. At it-agile, we have TDD camps where we teach TDD to others. http://www.it-agile.de/tddcamp.html I use Infinitest to demonstrate the concept of continuous testing.

The last time I did so was in January. On that occasion, I found that Infinitest had an annoying bug which caused it to get stuck at times. I later found that this bug already was in your bug tracker. I have not checked since. But I am starting another TDD camp tomorrow. If the bug persists, I will let you know.

I also found that excluding tests from being executed was too hard. I remember thinking that there was no way to do so. I later found an explanation how to filter tests based on class or package name. I find this insufficient. I would like to see a facility to filter tests based on source folder.

We generally recommend to put the fast tests (unit tests) in one source folder and the slow tests (integration tests) into another. The tests I want to use for immediate feedback on what I am doing are the unit tests. Unfortunately, the last time I checked I could not instruct Infinitest to ignore the slow integration tests.

Based on these two things, I did not recommend Infinitest for everyday use. But I told the workshop participants to keep an eye out for continuous testing in general and Infinitest in particular.

Besten Gruß,
Alex