Run Unit Tests

Running unit tests in Codefresh pipelines

As we have explained in the Unit tests page Codefresh supports several ways of running unit tests. The most usual scenarios are using an existing Docker Hub image (common with compiled languages such as Java and Go) or using the application image itself (common with languages such as JavaScript/Python/Ruby/PHP).

In this example we will see both ways using two different applications in a single pipeline.

Unit tests with Codefresh

Unit tests with Codefresh

In the first case we will run unit tests before creating the application docker image, while in the second case we will run unit tests inside the application Docker image.

The example Python/Go project

You can see the example project at The repository contains two applications (Python and Go) with their respective unit tests.

You can play with it locally by using Docker commands to package the applications.

Create a pipeline with Unit tests

Here is the whole pipeline:


version: '1.0'
  - prepare
  - 'Microservice A'
  - 'Microservice B'
    title: Cloning main repository...
    type: git-clone
    repo: 'codefreshdemo/cf-example-unit-test'
    revision: 'master'
    git: github
    stage: prepare
    title: Running Unit tests directly
    stage: 'Microservice A'
    image: golang:1.12
    working_directory: './golang-app-A'
      - go test -v
    title: Building Go Docker Image
    type: build
    stage: 'Microservice A'
    image_name: my-go-image
    working_directory: './golang-app-A'
    tag: 'master'
    dockerfile: Dockerfile
    title: Building Python Docker Image
    type: build
    stage: 'Microservice B'
    image_name: my-python-image
    working_directory: './python-app-B'
    tag: 'master'
    dockerfile: Dockerfile
    title: Running Unit tests inside App image
    stage: 'Microservice B'
    image: ${{build_before_my_tests}}
    working_directory: '/app'
      - python test   

This pipeline does the following:

  1. Clones the source code with a Git clone step
  2. Runs unit test for the GO application using the Dockerhub image golang:1.12
  3. Builds the Docker image for the Go application
  4. Builds the Docker image for the Python application
  5. Runs unit tests for the Python application using as runtime context the application image that was just created.

Notice that in the second case the tests run in the context of build_before_my_tests which is the name of the step that creates the Docker image for Python. See context variables for more information on this technique.

We generally recommend the first approach, so that your production Docker image does not contain any unit testing libraries or frameworks, but there is no right or wrong choice regarding the way you run unit tests.