How much code coverage do you really need?

http://software-development-thoughts.blogspot.ca/2011/04/how-much-code-coverage-do-you-really.html

Two quotes from Uncle Bob
“Two things. Repeatability and cost. Manual tests are horrifically expensive compared to automated tests.”

“Manual tests aren't tests; they are trials. And since there are humans involved, they are suspect."

TDD is about Development not Design

TDD is about Development not Design

In initial design stage, need to hide unrelated detail as much as possible, cover high level scenario only.

Test Driven Design forces thinking on low level details. In this way, it is very easy to lose focus.


Try a new project to see if TDD stands for Test Driven Development, or Test Driven Design

How to fix FakeitEasy problem The current proxy generator can not intercept the specified method for the following reason: Sealed methods can not be intercepted.

Add virtual keyword to the method
http://geekswithblogs.net/Aligned/archive/2013/03/12/fakeiteasy---sealed-methods-can-not-be-intercepted-exception.aspx

TDD Is About Design, Not Testing

"Writing tests after writing code is a corruption of TDD"
"The act of writing a unit test is more an act of design than of verification."
http://www.drdobbs.com/tdd-is-about-design-not-testing/229218691

TDD is a way to design software? or a way to verify/refine design? or both?

The most difficult part of TDD: You have to write tests first before coding/design/implementation

"Have to actually think what you expect from a piece of code BEFORE you write it! Madness! Instead of just writing code, you have to think before you code! And if you can't formulate properly an expectation, HOW do you write the code in the first place?!"

http://www.sapiensworks.com/blog/post/2013/07/17/-TDD-Is-Not-Slow.aspx