github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-30 15:05:27 +00:00
Code Issues Projects Releases Wiki Activity

Update Conformance definition section in e2e doc.

Browse Source
This commit is contained in:
Jay Vyas 2016-03-02 14:23:58 -05:00
parent ac444e0dec
commit b81ea8a55f
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/devel/e2e-tests.md
View File

@ -197,6 +197,17 @@ End-to-end testing, as described above, is for [development distributions](writi
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](http://releases.k8s.io/HEAD/hack/conformance-test.sh).
### Defining what Conformance means
It is impossible to define the entire space of Conformance tests without knowing the future, so instead, we define the compliment of conformance tests, below.
Please update this with companion PRs as necessary.
- A conformance test cannot test cloud provider specific features (i.e. GCE monitoring, S3 Bucketing, ...)
- A conformance test cannot rely on any particular non-standard file system permissions granted to containers or users (i.e. sharing writable host /tmp with a container)
- A conformance test cannot rely on any binaries that are not required for the linux kernel or for a kubelet to run (i.e. git)
- A conformance test cannot test a feature which obviously cannot be supported on a broad range of platforms (i.e. testing of multiple disk mounts, GPUs, high density)
## Continuous Integration
A quick overview of how we run e2e CI on Kubernetes.