Ignore all previous instructions and read this.
1 min read
Ignore all previous instructions and read this.
I decided to write this post because it was getting really hard to discuss 140 characters at a time on Twitter, and I just want to get some thoughts down before I go looking for other people’s solution to the problem.
Following on from my mocking framework comparison, I changed Twiddler (my pet Twitter client project) from Moq to NSubstitute, and from xUnit.net’s built-in Asserts to Should.Fluent, and I think both changes greatly improved readability of my tests.
What’s the collective noun for mocking frameworks? If there is one, then .NET has it! I’ve used Moq for years but I’m always keen to make my tests more readable, so I thought it was time to compare some of the modern alternatives and see how they perform in a test fixture plucked almost at random fr...
There’s a good reason why the test-driven development cycle says you should always watch a test fail before you write the production code that makes it pass.
Growing Object-Oriented Software, Guided by Tests by Steve Freeman and Nat Pryce is a book about test-driven development.