Files
weave/test
Matthias Radestock eebb674232 simplify dns tests
- use 'host' to lookup MX record. It's shorter
- use getent everywhere else for dns lookups, instead of dig; this
  tests more of the o/s name resolution machinery and is generally
  shorter.
- introduce assert_dns_record helper that performs forward and reverse
- lookup introduce some vars for holding constants, so we don't have
  to repeat them
2015-04-22 19:38:04 +01:00
..
2014-12-30 16:28:03 +00:00
2015-04-22 19:38:04 +01:00
2015-04-22 19:38:04 +01:00
2015-04-22 19:38:04 +01:00
2015-04-22 19:38:04 +01:00
2015-04-22 09:25:42 +01:00
2015-04-22 19:38:04 +01:00
2014-12-04 17:20:58 +00:00
2015-03-20 14:37:24 +00:00

This directory contains integration tests for weave.

Requirements

You need two VMs with docker >=1.3.1 installed and listening on TCP port 2375 (see below). You also need to be able to ssh to these VMs, preferably without having to input anything.

The Vagrantfile in this directory constructs two such VMs. To meet the aforementioned ssh requirement you may want to

cp ~/.vagrant.d/insecure_private_key .

Running tests

./setup.sh

uploads the weave images from where the Makefile puts them (/var/tmp) to the two docker hosts, and copies the weave script over.

Then you can use, e.g.,

./200_dns_test.sh

to run an individual test, or

./run_all.sh

to run everything named *_test.sh.

Using other VMs

By default the tests assume the Vagrant VMs are used.

To use other VMs, set the environment variable HOSTS to the space-separated list of IP addresses of the docker hosts, and set the environment variable SSH to a command that will log into either (which may just be ssh).

Making docker available over TCP

To make docker listen to a TCP socket, you will usually need to either run it manually with an option like -H tcp://0.0.0.0:2375; or, for apt-get installed docker (Ubuntu and Debian), add the line

DOCKER_OPTS="--host unix:///var/run/docker.sock --host tcp://0.0.0.0:2375"

to the file /etc/default/docker, then restart docker.