From b16ac5dc0e9dffd74410b2d2cfc80b57e92191bc Mon Sep 17 00:00:00 2001 From: Satnam Singh Date: Wed, 10 Sep 2014 21:29:44 -0700 Subject: [PATCH] Improve the documentation for end-to-end tests. --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4ed8b7549eb..6f26adeaa42 100644 --- a/README.md +++ b/README.md @@ -169,13 +169,17 @@ hack/test-integration.sh ### End-to-End tests -With a GCE account set up for running `cluster/kube-up.sh` (see Setup above): - +You can run an end-to-end test which will bring up a master and two minions, perform some tests, and then tear everything down. Make sure you have followed the getting started steps for your chosen cloud platform (which might involve changing the `KUBERNETES_PROVIDER` environment variable to something other than "gce". ``` cd kubernetes hack/e2e-test.sh ``` +Pressing control-C should result in an orderly shutdown but if something goes wrong and you still have some VMs running you can force a cleanup with the magical incantation: +``` +hack/e2e-test.sh 1 1 1 +``` + ### Testing out flaky tests [Instructions here](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/flaky-tests.md)