Service tests are automated tests executed against an instance of running service, usually after deployment, to ensure that the service works properly with other parts of the system. For example, if a service uses DB then we want to test its interface and ensure that the data from DB is returned.
In testing pyramid they are located between unit-test and end-to-end tests. The main target of those tests is service API so it's fairly easy to write them which makes them a crucial part of software quality assurance
This repository demonstrates one of the approaches to write, run and maintain service tests for a Golang service.
In this repo you will find:
- simple Rest API server
- service test for the API
- Docker file for service test build
- Script to build service test image
- Github Action pipeline to build and push service test image
We have our basic api service declared in router.go file with three methods:
GET /ping- returns 200 OK and pong in responseGET /boxes/{box_id}- returns Json with box content by it's IDPUT /boxes/{box_id}- updates box content by it's ID
We have a test that checks that our service works as expected. Test is written as a go tests the only difference is that we don't access any methods directly but use HTTP calls to call our service.
Running locally is good for one time verification. In order to run test as part of CI/CD pipeline we need to build and push service test image. To do that we will build a test binary first
env CGO_ENABLED=0 go test ./test/stest -tags servicetest -v -c -o bin/service-test
then we will build a docker image using Test.Dockerfile created specifically for service tests.
docker build -f Test.Dockerfile -t service-test .
You probably want to do it in a pipeline so here is an example of Github Action pipeline that does that for you.
We build application image with two tags [short-commit-sha] and [branch-name]-[build-number] test image is being built with the same tags but with -test suffix. That way we use same Docker repository for both application and test images. You may consider having separate repository although I would suggest to stick to some naming conventions. This will make it easier to deal with running the test later.
Our service test have a servicetest build tag that prevents our test from running with go test ./... command.
To run our test locally:
go test ./test/stest -tags servicetest -v -count=1
Test are packaged into a docker image so we can run them in a container. This docker container is easy to run in a K8s as part of helm test, k8s job, or as a step in a CD pipeline.
If you use helm charts to deploy you application then you can use helm test to run your service tests. Here is an example of helm test file.
The advantage of this approach is tha you can run test by executing helm test command.
Try this example in Kubernetes by running:
helm install int-example boxes-api
helm test int-example
kubectl logs int-example-boxes-api-test-service
The test results are reported in a log of a container.
However, if you want to aggregate test results and keep the history of execution then you make consider using testhub for that.