diff options
| author | Eric Tune <etune@google.com> | 2015-03-06 09:54:46 -0800 |
|---|---|---|
| committer | Eric Tune <etune@google.com> | 2015-03-30 09:52:52 -0700 |
| commit | d60aa36171ee57c3a2d0b02a8285c5f0e6107e9f (patch) | |
| tree | 2104a02f911ba478b76c6aaa209c68c63d25d399 /development.md | |
| parent | 9786c3c7634b5b6a54fcf9258660ae36c694d8d2 (diff) | |
Proposed guidelines for new Getting-started-guides.
# *** ERROR: *** docs are out of sync between cli and markdown
# run hack/run-gendocs.sh > docs/kubectl.md to regenerate
#
# Your commit will be aborted unless you regenerate docs.
COMMIT_BLOCKED_ON_GENDOCS
Diffstat (limited to 'development.md')
| -rw-r--r-- | development.md | 11 |
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) |