In this episode of Testing All The Things we refactor the test code we created in episodes 027 – 030. Replacing the hand coded test doubles with ones we create using the Go mocking framework GoMock.
The code produced during this episode can be found on GitHub
This episode of Testing All The Things we finish a series where we look at different forms of Test Doubles. We will look at a different type of Test Double in each of the videos. We will implement our own test doubles, we will not use a mocking framework.
We use Test Doubles to replace the dependencies a class uses in production so we have complete control over its dependencies enabling us to isolate the code under test from the implementation of its dependencies.
In the video we look at the Fake type of Test Double.
The code produced during the Test Doubles episodes can be found on GitHub
This episode of Testing All The Things we continue a series where we look at different forms of Test Doubles. We will look at a different type of Test Double in each of the videos. We will implement our own test doubles, we will not use a mocking framework.
We use Test Doubles to replace the dependencies a class uses in production so we have complete control over its dependencies enabling us to isolate the code under test from the implementation of its dependencies.
In the video we look at the Mock type of Test Double.
The code produced during the Test Doubles episodes can be found on GitHub
This episode of Testing All The Things we continue a series where we look at different forms of Test Doubles. We will look at a different type of Test Double in each of the videos. We will implement our own test doubles, we will not use a mocking framework.
We use Test Doubles to replace the dependencies a class uses in production so we have complete control over its dependencies enabling us to isolate the code under test from the implementation of its dependencies.
In the video we look at the Spy type of Test Double.
The code produced during the Test Doubles episodes can be found on GitHub
This episode of Testing All The Things is the first in a series where we look at different forms of Test Doubles. We will look at a different type of Test Double in each of the videos. We will implement our own test doubles, we will not use a mocking framework.
We use Test Doubles to replace the dependencies a class uses in production so we have complete control over its dependencies enabling us to isolate the code under test from the implementation of its dependencies. In the video we look at the Stub type of Test Double.
The code produced during the Test Doubles episodes can be found on GitHub
In this episode we continue to use Test && Commit || Revert (TCR). This way of practising TDD. The practise was developed by Oddmund Strømme and written about by Kent Beck
The practise encouraging writing a test then writing the implementation in tiny iterations by reverting all changes made since since the last time the tests passed.
During this video we implement complete Untangling Conditionals Kata by Tom Oram
The Jetbrains IntelliJ IDEA plugin we use during this video is called Limited WIP.
The code produced during this episode can be found on GitHub
In this episode we play with Test && Commit || Revert or TCR. This way of practising TDD. The practise was developed by Oddmund Strømme and written about by Kent Beck ():
The practise encouraging writing a test then writing the implementation in tiny iterations by reverting all changes made since since the last time the tests passed.
During this video we implement the FizzBuzz code kata using the TCR technique.
The Jetbrains IntelliJ IDEA plugin we use during this video is called Limited WIP.
The code produced during this episode can be found on GitHub
In this episode we look at the Hexagon Architecture approach we use to create the book api. We draw out a diagram to show how the different parts of our application fit within the Hexagon Architecture pattern.
In this episode we continue to use Test Driven Development (TDD) to drive out the implementation the simple HTTP REST(ish) API microservice in PHP.
We add handling when the database is not available to the endpoint GET to retrieve a book by its ISBN.
We start by refactoring the endpoint code to add different layers (Controller – Business Logic – Book Repository). We then add Unit and Integration tests to ensure our code ensure each part of our application can handle the different exceptions being thrown.
The code produced during this episode can be found on GitHub
During this video we use:
In this episode we continue to use Test Driven Development (TDD) to drive out the implementation the simple HTTP REST(ish) API microservice in PHP.
We add handling when a book is not available to the endpoint GET to retrieve a book by its ISBN.
Starting with an End to End Test write using PHP Unit and Guzzle HTTP Client for PHP to design out how consumers of the API will interact with the endpoint.
We then add an Integration test to ensure our code uses Doctrine PHP ORM to interact with the Postgres database to get the book data.
The code produced during this episode can be found on GitHub
During this video we use: