Skip to content

Latest commit

 

History

History
 
 

tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
access_test.go
access_test.go
 
 
console_test.go
console_test.go
 
 
controller_leader_election_test.go
controller_leader_election_test.go
 
 
expose_test.go
expose_test.go
 
 
ovm_test.go
ovm_test.go
 
 
registry_disk_test.go
registry_disk_test.go
 
 
replicaset_test.go
replicaset_test.go
 
 
storage_test.go
storage_test.go
 
 
subresource_api_test.go
subresource_api_test.go
 
 
test.go
test.go
 
 
tests_suite_test.go
tests_suite_test.go
 
 
utils.go
utils.go
 
 
version_test.go
version_test.go
 
 
vm_configuration_test.go
vm_configuration_test.go
 
 
vm_monitoring_test.go
vm_monitoring_test.go
 
 
vm_networking_test.go
vm_networking_test.go
 
 
vm_userdata_test.go
vm_userdata_test.go
 
 
vmdefaults_test.go
vmdefaults_test.go
 
 
vmlifecycle_test.go
vmlifecycle_test.go
 
 
vmpreset_test.go
vmpreset_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

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