From cfa19844f2756324d68d6b5a0b60c5c743a93b8e Mon Sep 17 00:00:00 2001 From: Ole Markus With Date: Sat, 18 Apr 2020 14:59:43 +0200 Subject: [PATCH] Update docs/development/testing.md Co-Authored-By: Ciprian Hacman --- docs/development/testing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/development/testing.md b/docs/development/testing.md index ed9d46ec72..f4b98dbd76 100644 --- a/docs/development/testing.md +++ b/docs/development/testing.md @@ -6,7 +6,7 @@ Unit and integration tests can be run using `go test` To run all tests: ``` -go test ./... +go test -v ./... ``` ### Adding an integration test @@ -51,4 +51,4 @@ GINKGO_PARALLEL=y kubetest --test --test_args="--ginkgo.skip=\[Slow\]|\[Serial\] If you want to run the tests against your development version of kops, you need to upload the binaries and set the environment variables as described in [Adding a new feature](adding_a_feature.md). -Since we assume you are using this cluster for testing, we leave the cluster running after the tests have finished so that you can inspect the nodes if anything unexpected happens. If you do not need this, you can add the `--down` flag. Otherwise, just delete the cluster as any other cluster: `kops delete cluster my.testcluster.com --yes` \ No newline at end of file +Since we assume you are using this cluster for testing, we leave the cluster running after the tests have finished so that you can inspect the nodes if anything unexpected happens. If you do not need this, you can add the `--down` flag. Otherwise, just delete the cluster as any other cluster: `kops delete cluster my.testcluster.com --yes`