Files
moby/libnetwork/test/integration
Madhu Venugopal 1419d96a01 Reducing the complexity in default gateway service handling
By removing the need to clear the default gateway during sbJoin and
sbLeave to account for other bridge network, the default-gw endpoint
will stay with the container, it will also help retain the container
property.

Signed-off-by: Madhu Venugopal <madhu@docker.com>
2016-01-23 11:10:00 -08:00
..

LibNetwork Integration Tests

Integration tests provide end-to-end testing of LibNetwork and Drivers.

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 to it through the CLI.

Note that integration tests do not replace unit tests and Docker is used as a good use-case.

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.

Pre-Requisites

  1. Bats (https://github.com/sstephenson/bats#installing-bats-from-source)
  2. Docker Machine (https://github.com/docker/machine)
  3. Virtualbox (as a Docker machine driver)

Running integration tests

In order to run all integration tests, pass bats the test path:

$ bats test/integration/daemon-configs.bats