Public | Automated Build

Last pushed: 7 months ago
Short Description
Short description is empty for this repo.
Full Description

Swarm Integration Tests

Integration tests provide end-to-end testing of Swarm.

While unit tests verify the code is working as expected by relying on mocks and
artificially created fixtures, integration tests actually use real docker
engines and communicate with Swarm through the CLI.

Note that integration tests do not replace unit tests.

As a rule of thumb, code should be tested thoroughly with unit tests.
Integration tests on the other hand are meant to test a specific feature end
to end.

Integration tests are written in bash using the
bats framework.

Running integration tests

The easiest way to run integration tests is with Docker:

$ test/integration/run.sh

Alternatively, you can run integration tests directly on your host:

$ bats test/integration

In order to do that, you will need to setup a full development environment plus
bats

Note: There are known issues running the integration tests using
devicemapper as a storage driver, make sure that your docker daemon
is using aufs if you want to successfully run the integration tests.

Writing integration tests

[helper functions]
(https://github.com/docker/swarm/blob/master/test/integration/helpers.bash)
are provided in order to facilitate writing tests.

#!/usr/bin/env bats

# This will load the helpers.
load helpers

# teardown is called at the end of every test
function teardown() {
    # This will stop the swarm manager:
    swarm_manage_cleanup

    # This will stop and remove all engines launched by the test:
    stop_docker
}

@test "this is a simple test" {
    # start_docker will start a given number of engines:
    start_docker 2

    # The address of those engines is available through $HOSTS:
    run docker -H ${HOSTS[0]} info
    # "run" automatically populates $status, $output and $lines.
    # Please refer to bats documentation to find out more.
    [ "$status" -eq 0 ]

    # You can start multiple docker engines in the same test:
    start_docker 1
    # Their address will be *appended* to $HOSTS. Therefore, since this is the 3rd
    # engine started, its index will be 2:
    run docker -H ${HOSTS[2]} info  

    # Additional parameters can be passed to the docker daemon:
    start_docker 1 --label foo=bar

    # swarm_manage will start the swarm manager, preconfigured with all engines
    # previously started by start_engine:
    swarm_manage

    # You can talk with said manager by using the docker_swarm helper:
    run docker_swarm info
    [ "$status" -eq 0 ]
    [ "${lines[1]}"="Nodes: 4" ]
}
Docker Pull Command
Owner
dockerswarm
Source Repository

Comments (0)