Most developers don't run tests after they change code. This is mostly about habit, but also about perceived inconvenience, I imagine. There's an easy way to get around that... make VS smart enough to have tests automatically run in the background when the code they're testing is changed (and obviously recompiled). To do this, there might need to be a way to specify what class members are tested in each test method, but that'd be good anyway. I find myself putting that in all test method comments, anyway. Whether that's added via a code comment or attribute, I don't care; although, the latter makes a little more sense.