c3c4825f80
A local endpoint is known to the watch database only during Join. But the same endpoint can be known to the watch database as remote endpoint well before the Join because a CreateEndpoint updates the endpoint to the store. So on Join when you come to know that this is indeed a local endpoint remove it from remote endpoint list and add it to local endpoint list. Signed-off-by: Jana Radhakrishnan <mrjana@docker.com> |
||
|---|---|---|
| .. | ||
| dnet | ||
| README.md | ||
| daemon-configs.bats | ||
| daemon.cfg | ||
| helpers.bash | ||
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