Skip to content

Files

Latest commit

7c5284e · Dec 18, 2018

History

History

tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Dec 17, 2018
Dec 17, 2018
Oct 10, 2018
Dec 4, 2018
Dec 4, 2018
Dec 4, 2018
Dec 17, 2018
Dec 11, 2018
Dec 4, 2018
Dec 4, 2018
Dec 16, 2018
Dec 4, 2018
Dec 4, 2018
Dec 4, 2018
Dec 4, 2018
Dec 1, 2018
Dec 14, 2018
Dec 4, 2018
Oct 15, 2018
Aug 2, 2017
Dec 4, 2018
Dec 18, 2018
Oct 15, 2018
Dec 4, 2018
Dec 13, 2018
Dec 4, 2018
Dec 4, 2018
Dec 4, 2018
Dec 10, 2018
Dec 4, 2018
Dec 11, 2018
Dec 18, 2018
Dec 4, 2018
Dec 4, 2018
Dec 4, 2018
Dec 4, 2018
Dec 4, 2018
Dec 4, 2018

Integration tests

Integration tests require a running Kubevirt cluster. Once you have a running Kubevirt cluster, you can use the -master and the -kubeconfig flags to point the tests to the cluster.

Run them on an arbitrary KubeVirt installation

cd tests # from the git repo root folder
go test -kubeconfig=path/to/my/config

Run them on one of the core KubeVirt providers

There is a make target to run this with the config taken from hack/config.sh:

# from the git repo root folder
make functest

Run them anywhere inside of container

# Create directory for data / results / kubectl binary
mkdir -p /tmp/kubevirt-tests-data
# Make sure that eveybody can write there
setfacl -m d:o:rwx /tmp/kubevirt-tests-data
setfacl -m o:rwx /tmp/kubevirt-tests-data

docker run \
    -v /tmp/kubevirt-tests-data:/home/kubevirt-tests/data:rw,z --rm \
    kubevirt/tests:latest \
        --kubeconfig=data/openshift-master.kubeconfig \
        --container-tag=latest \
        --container-prefix=docker.io/kubevirt \
        --test.timeout 180m \
        --junit-output=data/results/junit.xml \
        --deploy-testing-infra \
        --path-to-testing-infra-manifests=data/manifests