+1

I think cutest should keep the default behaviour of failing fast. It's very useful while developing.

Running all tests regardless of there being failures would be very useful for running automated tests on a CI server for example.

Cool. Yeah, I agree with you. And keeping the default behaviour makes the change backwards compatible. I'll invert the flag (or how should it be called then?).

@djanowski any comments here? I can just flip the flag if you're ok going ahead with #28.

@gtramontina The flag can be -c (continue).

Hard to come up with the right name. I was thinking maybe -f (force) or -a (all).

-a for all seems sensible.

I think the usage string (in the executable) should be clearer, though. [-a] is not very clear on what it means.

We already have -s and -o to filter what Cutest should run. -a for "all" seems to compete with that.

I'm still inclined for -c (continue).