History

Jana Radhakrishnan ab0c0df288 Add IT case for external connectivity Added IT cases for external connectivity check for bridge and overlay networks, both initially and after a restart. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>		2015-10-28 19:10:38 -07:00
..
dnet	Add IT case for external connectivity	2015-10-28 19:10:38 -07:00
README.md	Initial bats based integration tests for testing daemon network configs	2015-04-25 07:33:48 -07:00
daemon-configs.bats	Initial bats based integration tests for testing daemon network configs	2015-04-25 07:33:48 -07:00
daemon.cfg	Initial bats based integration tests for testing daemon network configs	2015-04-25 07:33:48 -07:00
helpers.bash	Initial bats based integration tests for testing daemon network configs	2015-04-25 07:33:48 -07:00

README.md

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

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

Running integration tests

Start by [installing] (https://github.com/sstephenson/bats#installing-bats-from-source) bats on your system.
If not done already, install docker-machine into /usr/bin
Make sure Virtualbox is installed as well, which will be used by docker-machine as a driver to launch VMs

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

$ bats test/integration/daemon-configs.bats