From 2b3ad6e1793ada594cfe0af209bb34947725cee7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20Str=C3=B6mberg?= Date: Wed, 20 Mar 2019 19:36:06 -0700 Subject: [PATCH] Mention integration env overrides --- docs/contributors/build_guide.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/contributors/build_guide.md b/docs/contributors/build_guide.md index 67a12be71a..171a6961ca 100644 --- a/docs/contributors/build_guide.md +++ b/docs/contributors/build_guide.md @@ -55,7 +55,7 @@ Start the cluster using your built minikube with: $ ./out/minikube start ``` -### Running Tests +## Running Tests #### Unit Tests @@ -65,7 +65,7 @@ Unit tests are run on Travis before code is merged. To run as part of a developm make test ``` -#### Integration Tests +### Integration Tests Integration tests are currently run manually. To run them, build the binary and run the tests: @@ -74,7 +74,13 @@ To run them, build the binary and run the tests: make integration ``` -#### Conformance Tests +You may find it useful to set various options to test only a particular test against a non-default driver. For instance: + +```shell + env TEST_ARGS="-minikube-start-args=--vm-driver=hyperkit -test.run TestStartStop" make integration + ``` + +### Conformance Tests These are Kubernetes tests that run against an arbitrary cluster and exercise a wide range of Kubernetes features. You can run these against minikube by following these steps: