The is a third in a series of screencasts in which we look at API and Microservice testing framework called Pact.
In this video we start looking sharing Pact files between Consumer and Provider via a Pact Broker. We use https://pactflow.io/ as our Broker rather than running out own.
The code produced during this episode can be found on GitHub: https://github.com/testingallthethings/038-pact-http-consumer-go https://github.com/testingallthethings/033-go-rest
The is a second in a series of screencast in which we look at API and Microservice testing framework called Pact.
In this video we start looking at using Pact to test drive the implementation of a HTTP producer in Golang.
The code produced during this episode can be found on GitHub
The is a first in a series of screencasts in which we look at API and Microservice testing framework called Pact.
In this video we start looking at using Pact to test drive the implementation of a HTTP consumer in of our Book API in Golang.
This recording end a bit abruptly as I took a phone call and forgot to restart recording for the last few minutes of explaining the pact file.
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.
The code produced during this episode can be found on GitHub
In this episode of Testing All The Things we continues to use Test Driven Development (TDD) to drive out the implementation the simple HTTP REST(ish) API in Go using Gorilla Mux.
In this video we use end to end testing to drive out the functionality to validate the ISBN that is requested. During the video we create a Business Logic layer to validate the incoming ISBN to separate the knowledge of the HTTP layer into the REST Handler and keep the database code in its own code. We use Unit Tests to drive out the implementation of the new business logic code.
The code produced during this episode can be found on GitHub
In this episode of Testing All The Things we continues to use Test Driven Development (TDD) to drive out the implementation the simple HTTP REST(ish) API in Go using Gorilla Mux.
In this video we use Unit and Integration test to move the code that gets book data from the database into different places. We first create a HTTP Handler using Unit test. In the second part we create something to retrieve a book from the database by its ISBN using integration tests. Finally we remove the old code that our end to end test drove out in the previous video and get the application working with the new code we write in this episode.
The code produced during this episode can be found on GitHub
In this episode of Testing All The Things we continues to use Test Driven Development (TDD) to drive out the implementation the simple HTTP REST(ish) API in Go using Gorilla Mux.
The second feature we add is a new endpoint to GET the book by ISBN of the Microservice. Starting with an End to End Test write using Testify and Go HTTP Client to design out how consumers of the API will interact with the /book/{isbn} endpoint.
The code produced during this episode can be found on GitHub
In this episode of Testing All The Things we start to use Test Driven Development (TDD) to drive out the implementation the simple HTTP REST(ish) API in Go using Gorilla Mux.
The first feature we add is a new endpoint to GET the health of the Microservice. Starting with an End to End Test write using Testify and Go HTTP Client to design out how consumers of the API will interact with the /healthcheck endpoint.
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: