Reputation
266
Top tag
Next privilege 300 Rep.
Create new tags
Badges
2 6
Newest
 Nice Answer
Impact
~67k people reached

  • 0 posts edited
  • 0 helpful flags
  • 1 vote cast
Mar
8
awarded  Nice Answer
Jan
26
awarded  Nice Answer
Jan
4
awarded  Yearling
Nov
7
awarded  Critic
Jan
31
awarded  Supporter
Jan
31
comment How much Code Coverage is “enough”?
Upvote for the comment about removing code. I use code coverage metrics for that all the time (in VS, where it highlights the lines that aren't covered).
Jan
31
comment How much Code Coverage is “enough”?
I think this is a false choice. High-quality tests that only touch a small amount of code are poor overall measures of quality, as are "tests" that touch a large amount of code but don't really check results. Put another way, imagine a quality assurance process for cars that was very thorough at testing the front driver's-side wheel, but no other part of the car. That would be bad in the same way as a QA process that was just a guy eyeballing the whole car and saying "yeah, looks good."
Oct
20
comment How much Code Coverage is “enough”?
A lot of it stems from the fact that WPF input is hard to fake. Our testing is as unit-y or API-y as we can get it, and the inability to easily fake the layer that sits "on top" of WPF (input, at least) makes it difficult to test. It isn't a huge problem, as the non-GUI parts of the API are easy to test, but it's just that last stretch that goes from our model (or view model) to WPF that is challenging.
Oct
14
awarded  Enthusiast
Sep
9
awarded  Teacher
Sep
9
answered How much Code Coverage is “enough”?
Sep
9
answered What's the career path for a developer who doesn't like management?
Sep
9
answered Do people in non-English-speaking countries code in English?
Sep
9
awarded  Autobiographer