cri-o/test
Antonio Murdaca ab8b65b09e
test: cleanup pods at test teardown
Signed-off-by: Antonio Murdaca <runcom@redhat.com>
2016-09-27 10:46:50 +02:00
..
testdata test: fix and add tests 2016-09-27 10:42:53 +02:00
helpers.bash test: cleanup pods at test teardown 2016-09-27 10:46:50 +02:00
pod.bats test: cleanup pods at test teardown 2016-09-27 10:46:50 +02:00
README.md test: add README.md 2016-09-24 09:59:27 +02:00
runtimeversion.bats test: cleanup pods at test teardown 2016-09-27 10:46:50 +02: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

The easiest way to run integration tests is with Docker:

$ make integration

Alternatively, you can run integration tests directly on your host through make:

$ sudo make localintegration

Or you can just run them directly using bats

$ sudo bats test

To run a single test bucket:

$ make integration TESTFLAGS="runtimeversion.bats"

To run them on your host, you will 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

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() {
	stop_ocid
	cleanup_test
}

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