|
|
||
|---|---|---|
| .. | ||
| testdata | ||
| README.md | ||
| a_serial_test.go | ||
| addons_test.go | ||
| docker_test.go | ||
| driver_install_or_update_test.go | ||
| fn_mount_cmd.go | ||
| fn_pvc.go | ||
| fn_tunnel_cmd.go | ||
| functional_test.go | ||
| guest_env_test.go | ||
| gvisor_addon_test.go | ||
| helpers.go | ||
| main.go | ||
| none_test.go | ||
| start_stop_delete_test.go | ||
| util.go | ||
| version_upgrade_test.go | ||
README.md
Integration tests
The basics
To run all tests from the minikube root directory:
make integration
Quickly iterating on a single test
Run a single test on an active cluster:
make integration -e TEST_ARGS="-test.run TestFunctional/parallel/MountCmd --profile=minikube --cleanup=false"
WARNING: For this to work repeatedly, the test must be written so that it cleans up after itself.
See main.go for details.
Disabling parallelism
make integration -e TEST_ARGS="-test.parallel=1"
Testing philosophy
- Tests should be so simple as to be correct by inspection
- Readers should need to read only the test body to understand the test
- Top-to-bottom readability is more important than code de-duplication
Tests are typically read with a great air of skepticism, because chances are they are being read only when things are broken.