summaryrefslogtreecommitdiff
path: root/development.md
diff options
context:
space:
mode:
authorJeff Grafton <ixdy@users.noreply.github.com>2015-03-30 15:35:37 -0700
committerJeff Grafton <ixdy@users.noreply.github.com>2015-03-30 15:35:37 -0700
commit5ed385b9e7a2af8a3e132e8c82d86772d34608ce (patch)
treeda258a8561fe2c4e73bb1c07b8f861bdada01fba /development.md
parent636062818feee072bf5eac1636bff2df1f9e4848 (diff)
parentd60aa36171ee57c3a2d0b02a8285c5f0e6107e9f (diff)
Merge pull request #5141 from erictune/gsgrules
Guidelines for Getting Started Guide contributions
Diffstat (limited to 'development.md')
-rw-r--r--development.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/development.md b/development.md
index ef7c7ce8..7972eef6 100644
--- a/development.md
+++ b/development.md
@@ -227,6 +227,17 @@ go run hack/e2e.go -v -ctl='get events'
go run hack/e2e.go -v -ctl='delete pod foobar'
```
+## Conformance testing
+End-to-end testing, as described above, is for [development
+distributions](../../docs/devel/writing-a-getting-started-guide.md). A conformance test is used on
+a [versioned distro](../../docs/devel/writing-a-getting-started-guide.md).
+
+The conformance test runs a subset of the e2e-tests against a manually-created cluster. It does not
+require support for up/push/down and other operations. To run a conformance test, you need to know the
+IP of the master for your cluster and the authorization arguments to use. The conformance test is
+intended to run against a cluster at a specific binary release of Kubernetes.
+See [conformance-test.sh](../../hack/conformance-test.sh).
+
## Testing out flaky tests
[Instructions here](flaky-tests.md)