Mirror/k3s
1
0
Fork 0
mirror of https://github.com/k3s-io/k3s.git synced 2024-06-07 19:41:36 +00:00
Code Issues Packages Projects Releases Wiki Activity
db3c569b7f
k3s/tests/e2e
History
Brad Davidson db3c569b7f Add docker e2e test 
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
2022-08-05 02:39:25 -07:00
..
amd64_resource_files E2E: Dualstack test (#5617) 2022-06-14 08:40:29 -07:00
arm_resource_files Add nightly automation tests 2021-07-30 11:43:28 -07:00
docker Add docker e2e test 2022-08-05 02:39:25 -07:00
dualstack E2E: Dualstack test (#5617) 2022-06-14 08:40:29 -07:00
scripts E2E: Dualstack test (#5617) 2022-06-14 08:40:29 -07:00
secretsencryption E2E: Dualstack test (#5617) 2022-06-14 08:40:29 -07:00
splitserver E2E: Dualstack test (#5617) 2022-06-14 08:40:29 -07:00
upgradecluster E2E: Dualstack test (#5617) 2022-06-14 08:40:29 -07:00
validatecluster Add docker e2e test 2022-08-05 02:39:25 -07:00
Dockerfile.build [master] changing package to k3s-io (#4846) 2022-03-02 15:47:27 -08:00
README.md E2E: Dualstack test (#5617) 2022-06-14 08:40:29 -07:00
testutils.go E2E: Dualstack test (#5617) 2022-06-14 08:40:29 -07:00
vagrantdefaults.rb Add docker e2e test 2022-08-05 02:39:25 -07:00

README.md

End-to-End (E2E) Tests

E2E tests cover multi-node K3s configuration and administration: bringup, update, teardown etc. across a wide range of operating systems. E2E tests are run nightly as part of K3s quality assurance (QA).

Framework

End-to-end tests utilize Ginkgo and Gomega like the integration tests, but rely on Vagrant to provide the underlying cluster configuration.

Currently tested operating systems are:

Format

All E2E tests should be placed under tests/e2e/<TEST_NAME>.
All E2E test functions should be named: Test_E2E<TEST_NAME>.
A E2E test consists of two parts:

  1. Vagrantfile: a vagrant file which describes and configures the VMs upon which the cluster and test will run
  2. <TEST_NAME>.go: A go test file which calls vagrant up and controls the actual testing of the cluster

See the validate cluster test as an example.

Running

Generally, E2E tests are run as a nightly Jenkins job for QA. They can still be run locally but additional setup may be required. By default, all E2E tests are designed with libvirt as the underlying VM provider. Instructions for installing libvirt and its associated vagrant plugin, vagrant-libvirt can be found here. VirtualBox is also supported as a backup VM provider.

Once setup is complete, all E2E tests can be run with:

go test -timeout=15m ./tests/e2e/... -run E2E

Tests can be run individually with:

go test -timeout=15m ./tests/e2e/validatecluster/... -run E2E
#or
go test -timeout=15m ./tests/e2e/... -run E2EClusterValidation

Additionally, to generate junit reporting for the tests, the Ginkgo CLI is used. Installation instructions can be found here.

To run the all E2E tests and generate JUnit testing reports:

ginkgo --junit-report=result.xml ./tests/e2e/...

Note: The go test default timeout is 10 minutes, thus the -timeout flag should be used. The ginkgo default timeout is 1 hour, no timeout flag is needed.

Debugging

In the event of a test failure, the cluster and VMs are retained in their broken state. Startup logs are retained in vagrant.log.
To see a list of nodes: vagrant status
To ssh into a node: vagrant ssh <NODE>
Once you are done/ready to restart the test, use vagrant destroy -f to remove the broken cluster.