In episode 2 of Testing All The Things we start to exploring Test Doubles. Test doubles are used to isolate the code under test from its dependencies. Test doubles imitate the functionality of a dependency.
Creating test doubles do not require the use of a mocking framework. In the following videos we will not use a mocking framework so we can concentrate of the theory.
In the first video we are looking at the simplest form of Test Double, Stubs.
In the first episode of Testing All The Things we introduce the concept of Test Driven Development (TDD). Using unit tests to guide the implementation of a Queue (Abstract Data Type)
During this episode we follow Uncle Bob’s three Rules of TDD
- You are not allowed to write any production code unless it is to make a failing unit test pass.
- You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures.
- You are not allowed to write any more production code than is sufficient to pass the one failing unit test.
The GitHub repository for the code produced during this video can be found here.
For a while now I’ve been thinking about producing content other than a blog. So with that in mind I’ve been working on a series of coding screencasts about software testing.
Testing All The Things is my coding screencast that I will use to demonstrate different techniques and tools for automated testing software.
I plan to do broadcast live coding once I get a bit more practise but for now I will record the coding sessions then upload them to YouTube fortnightly.
The code produced during my coding demonstrations will be uploaded to the Testing All The Things GitHub account.
There is also a new Twitter account to follow as well if you want more tweets about coding and testing rather than cycling and family.
If you have any suggestions for things you would like me to cover please leave a comment on this post.
Look out for the first video tomorrow.