How to achieve 100% code coverage

Posted on 23 April 2011 by Peter Hendriks

A little while ago, “Uncle” Bob Martin respun a little debate regarding code coverage (measurement of code executed at least once when testing). According to Uncle Bob, 100% test coverage is a minimum requirement. In our industy, that is a Continue reading →

Gherkin & WatiN, a love story

Posted on 5 April 2010 by Tim Mahy

Gherkin is a Business Readable DSL language that let you describe behavior without having to know how it’s being accomplished. WatiN is a .NET framework to automate “Web Application Testing”. So, that’s enough for an introduction. The whole next blog Continue reading →

Stubs & Mocks meet their new friends: the Moles

Posted on 1 March 2010 by Tim Mahy

AKA ‘replace any static method call with a lamda allowing you to test first’ I’m, like many others, a strong believer of TDD, DRY, Build Only Business and Do The Simplest Thing That Could Possibly Work. However sometimes they don’t Continue reading →

Not doing something costs time and money, too

Posted on 1 February 2009 by Peter Hendriks

A recent podcast of Joel "On Software" Spolsky and Jeff "Stackoverflow" Atwood stirred up a bit of a debate. Joel goes into a big rant against Unit Tests and the SOLID design principles. Robert "Uncle Bob" C. Martin, author of Continue reading →

Peek into the database during your unit test

Posted on 29 September 2006 by Frank Bakker

Have you ever had the following problem? You are debugging a unit test which has just inserted some records into your database. While the unit test is waiting on a breakpoint you want to see the result of the insert in Continue reading →