cri-o/test
Dan Williams 9c44933b58 build: create a local GOPATH if none specified
Instead of requiring the developer to set up their own GOPATH somewhere,
do like Kubernetes and OpenShift Origin do:

git clone xxxxx
cd xxxxx
make

by creating an _output/ directory and linking the local source tree
into it, and setting that to be the GOPATH.

Signed-off-by: Dan Williams <dcbw@redhat.com>
2017-03-30 15:01:22 -05:00
..
bin2img build: create a local GOPATH if none specified 2017-03-30 15:01:22 -05:00
checkseccomp build: create a local GOPATH if none specified 2017-03-30 15:01:22 -05:00
copyimg build: create a local GOPATH if none specified 2017-03-30 15:01:22 -05:00
testdata Default all container storage to /var/lib/containers/storage 2017-03-24 08:19:08 -04:00
apparmor.bats test: enable tests in Travis 2017-01-19 19:14:46 +01:00
ctr.bats test: enable tests in Travis 2017-01-19 19:14:46 +01:00
helpers.bash make: revert switch to 'go install' 2017-02-17 03:22:12 +11:00
image.bats storage: fix image retrieval by id 2017-01-31 16:32:30 +01:00
network.bats test: enable tests in Travis 2017-01-19 19:14:46 +01:00
pod.bats test: enable tests in Travis 2017-01-19 19:14:46 +01:00
policy.json Integrate containers/storage 2017-01-18 10:23:30 -05:00
README.md test: Update and organize README 2017-01-26 23:21:12 +01:00
restore.bats test: enable tests in Travis 2017-01-19 19:14:46 +01:00
runtimeversion.bats test: add more debugging output 2016-10-02 19:13:00 +11:00
seccomp.bats test: enable tests in Travis 2017-01-19 19:14:46 +01:00
test_runner.sh add tests skeleton 2016-09-24 00:37:07 +02:00

OCID Integration Tests

Integration tests provide end-to-end testing of OCID.

Note that integration tests do not replace unit tests.

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.

Running integration tests

Containerized tests

The easiest way to run integration tests is with Docker:

$ make integration

To run a single test bucket:

$ make integration TESTFLAGS="runtimeversion.bats"

On your host

To run the integration tests on your host, you will first need to setup a development environment plus bats For example:

$ cd ~/go/src/github.com
$ git clone https://github.com/sstephenson/bats.git
$ cd bats
$ ./install.sh /usr/local

Then you can run the tests on your host:

$ sudo make localintegration

To run a single test bucket:

$ make localintegration TESTFLAGS="runtimeversion.bats"

Or you can just run them directly using bats

$ sudo bats test

Runtime selection

Tests on the host will run with runc as the default runtime. However you can select other OCI compatible runtimes by setting the RUNTIME environment variable.

For example one could use the Clear Containers runtime instead of runc:

make localintegration RUNTIME=cc-oci-runtime

Writing integration tests

[Helper functions] (https://github.com/kubernetes-incubator/ocid/blob/master/test/helpers.bash) are provided in order to facilitate writing tests.

#!/usr/bin/env bats

# This will load the helpers.
load helpers

# setup is called at the beginning of every test.
function setup() {
}

# teardown is called at the end of every test.
function teardown() {
	cleanup_test
}

@test "ocic runtimeversion" {
	start_ocid
	ocic runtimeversion
	[ "$status" -eq 0 ]
}