kotovalexarian-likes-github
/
moby--moby
mirror of https://github.com/moby/moby.git
1
0
Fork 0
Code Releases Activity
moby--moby/libnetwork/test/integration
History
Jana Radhakrishnan 888f13d17b Make the integration tests robust 
Currently integration test is a bit flaky because of
variability in the dnet bootup time. Fixed it to wait for
dnet to come up before performing any tests.

Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>
 		2015-10-09 00:06:51 -07:00
..
dnet Make the integration tests robust 2015-10-09 00:06:51 -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

  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