2 ms·
Perhaps I should rephrase. If you're trying to effectively unit test a project, when do you decide you've tested enough? And are there any metrics which help su
by joshvm 7y ago
Perhaps I should rephrase. If you're trying to effectively unit test a project, when do you decide you've tested enough? And are there any metrics which help support that?
Coverage for example is a weak signal that you've at least run some fraction of your codebase at test time.
- codeulike 7y agoI just write tests for the bits that I know I'm going to have lots of trouble with. You can tell, after a while