Anders Hovmöller
Anders Hovmöller
I guess I'd be ok with a fallback to something that just updates once per checked mutant on systems where I can't get the streaming output catching to work (including...
Yes please! Thanks for this insight.
This seems like a test runner feature, not a feature of a mutation tester. Or so I thought when I implemented this exact feature into hammett (my test runner) to...
The problem with putting it at the mutation tester level is that there really is no common API for test runners to get the required information from the runner, nor...
Ah, yea you only mean on the entire test file level, then yes, I believe it's fairly safe/easy to implement. We used to do this on iommi (for mutmut but...
@lvdstam we don't have the same mutants though, so don't be fooled into thinking that's the only difference between the tools! Also, you can sometimes get 10x or 100x improvements...
With hammett there doesn't need to be any communication (you can modify the command like before if you want but you shouldn't need to). Hammett checks the modification times of...
In process is pretty dangerous though. I found out that the hard way. That's why I run just 100 runs before I cycle the process. At least pytest-django (probably django)...
@lvdstam could you open issues for hammett and/or mutmut so we can continue discussing that there? You don't have an email-address so can't contact you directly. Sorry about this last...
Yea, tox/pip is extremely slow on startup. I've suffered in other projects because of this :( I like the idea of multiple runners! Normally I just mark python 2 as...