Skip to content

Latest commit

 

History

History
 
 

tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
containerdisk
containerdisk
 
 
flags
flags
 
 
network
network
 
 
reporter
reporter
 
 
BUILD.bazel
BUILD.bazel
 
 
Dockerfile
Dockerfile
 
 
OWNERS
OWNERS
 
 
README.md
README.md
 
 
access_test.go
access_test.go
 
 
config.go
config.go
 
 
config_test.go
config_test.go
 
 
console_test.go
console_test.go
 
 
container_disk_test.go
container_disk_test.go
 
 
datavolume_test.go
datavolume_test.go
 
 
default-config.json
default-config.json
 
 
entrypoint.sh
entrypoint.sh
 
 
expose_test.go
expose_test.go
 
 
imageupload_test.go
imageupload_test.go
 
 
infra_test.go
infra_test.go
 
 
job.go
job.go
 
 
kubectl_test.go
kubectl_test.go
 
 
migration_test.go
migration_test.go
 
 
networkpolicy_test.go
networkpolicy_test.go
 
 
operator_test.go
operator_test.go
 
 
pausing_test.go
pausing_test.go
 
 
ping.go
ping.go
 
 
probes_test.go
probes_test.go
 
 
replicaset_test.go
replicaset_test.go
 
 
security_features_test.go
security_features_test.go
 
 
snapshot_test.go
snapshot_test.go
 
 
stability_test.go
stability_test.go
 
 
storage_test.go
storage_test.go
 
 
subresource_api_test.go
subresource_api_test.go
 
 
template_test.go
template_test.go
 
 
test.go
test.go
 
 
tests_suite_test.go
tests_suite_test.go
 
 
utils.go
utils.go
 
 
version_test.go
version_test.go
 
 
virt_control_plane_test.go
virt_control_plane_test.go
 
 
vm_test.go
vm_test.go
 
 
vm_watch_test.go
vm_watch_test.go
 
 
vmi_cloudinit_hook_sidecar_test.go
vmi_cloudinit_hook_sidecar_test.go
 
 
vmi_cloudinit_test.go
vmi_cloudinit_test.go
 
 
vmi_configuration_test.go
vmi_configuration_test.go
 
 
vmi_gpu_test.go
vmi_gpu_test.go
 
 
vmi_headless_test.go
vmi_headless_test.go
 
 
vmi_hook_sidecar_test.go
vmi_hook_sidecar_test.go
 
 
vmi_ignition_test.go
vmi_ignition_test.go
 
 
vmi_iothreads_test.go
vmi_iothreads_test.go
 
 
vmi_lifecycle_test.go
vmi_lifecycle_test.go
 
 
vmi_monitoring_test.go
vmi_monitoring_test.go
 
 
vmi_multiqueue_test.go
vmi_multiqueue_test.go
 
 
vmi_multus_test.go
vmi_multus_test.go
 
 
vmi_networking_test.go
vmi_networking_test.go
 
 
vmi_slirp_interface_test.go
vmi_slirp_interface_test.go
 
 
vmidefaults_test.go
vmidefaults_test.go
 
 
vmipreset_test.go
vmipreset_test.go
 
 
vnc_test.go
vnc_test.go
 
 
windows_test.go
windows_test.go
 
 

README.md

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 -config=default-config.json

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