github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-05 11:12:03 +00:00
Code Issues Projects Releases Wiki Activity

Update conformance test policy

Browse Source 
Mostly doc updates and cruft removal

- describe conformance test policy and howto in e2e-tests.md
- rm e2e test info from testing.md in the name of DRY
- rm cluster/test-conformance.sh; unusable in release tar, not e2e.go
- update e2e test link in write-a-getting-started-guide.md
This commit is contained in:
Aaron Crickenberger
2016-03-22 13:09:31 -07:00
parent 2bb6f74bf9
commit 0dc1f5da04
4 changed files with 29 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

50
docs/devel/testing.md
View File

@@ -174,55 +174,7 @@ hack/test-integration.sh # Run all integration tests.
## End-to-End tests
* e2e tests build kubernetes and deploy a cluster of nodes.
- Generally on a specific cloud provider.
* Access gcr.io images
* Access a specific, non-latest image tag (unless testing pulling).
* Tests may not flake due to intermittent issues.
* Use ginko to desribe steps.
- See [should run a job to completion when tasks succeed](../../test/e2e/job.go)
* Use [NewDefaultFramework](../../test/e2e/framework.go)
- Contains clients, namespace and auto resource cleanup
* See [coding conventions](coding-conventions.md).
### e2e test philosophy
In general passing unit and integration tests should provide sufficient
confidence to allow code to merge. If that is not the case,
please *invest more time adding unit and integration test coverage*.
These tests run faster and have a smaller failure domain.
However, end-to-end (e2e) tests provide maximum confidence that
the system is working in exchange for reduced performance and a
higher debugging cost.
e2e tests deploy a real kubernetes cluster of real nodes on a concrete provider
such as GCE. The tests then manipulate the cluster in certain ways and
assert the expected results.
For a more in depth discussion please read [End-to-End Testing in Kubernetes](e2e-tests.md).
### Running e2e tests
```sh
cd kubernetes
go run hack/e2e.go -v --build --up --test --down
# Change code, run unit and integration tests
# Push to an existing cluster, or bring up a cluster if it's down.
go run hack/e2e.go -v --pushup
# Run all tests on an already up cluster
go run hack/e2e.go -v --test
# Run only conformance tests
go run hack/e2e.go -v -test --test_args="--ginkgo.focus=\[Conformance\]"
# Run tests on a specific provider
KUBERNETES_PROVIDER=aws go run hack/e2e.go --build --pushup --test --down
```
For a more in depth discussion please read [End-to-End Testing in Kubernetes](e2e-tests.md).
Please refer to [End-to-End Testing in Kubernetes](e2e-tests.md).
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/testing.md?pixel)]()