@peterdrake
How would you measure the frequency of tests run?
By time passed, number of modified lines, number of modified files?
@peterdrake
This could be implemented in an ide, directly advising you to run tests; however you would have to train it by telling him how many bugs you have introduced each time you run your tests
@rastinza I think some have it set up to run the tests every time you compile or commit.
@rastinza It feels like modified lines is closest to "how much have you changed the software", which is the best estimate for "how many bugs did you introduce". That said, it's probably more dangerous if the ten lines you modified are in ten different files.
My main point is to urge people to run their tests more often.