diff options
| -rw-r--r-- | contributors/guide/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/guide/README.md b/contributors/guide/README.md index d2027344..1b9d12ce 100644 --- a/contributors/guide/README.md +++ b/contributors/guide/README.md @@ -179,7 +179,7 @@ Testing is the responsibility of all contributors and is in part owned by all si The main testing overview document is [here](/contributors/devel/testing.md). -There are three types of test in kubernetes. The location of the test code varies with type, as does the specifics of the environment needed to successfully run the test: +There are three types of tests in kubernetes. The location of the test code varies with type, as do the specifics of the environment needed to successfully run the test: * Unit: These confirm that a particular function behaves as intended. Golang includes a native ability for unit testing via the [testing](https://golang.org/pkg/testing/) package. Unit test source code can be found adjacent to the corresponding source code within a given package. For example: functions defined in [kubernetes/cmd/kubeadm/app/util/version.go](https://git.k8s.io/kubernetes/cmd/kubeadm/app/util/version.go) will have unit tests in [kubernetes/cmd/kubeadm/app/util/version_test.go](https://git.k8s.io/kubernetes/cmd/kubeadm/app/util/version_test.go). These are easily run locally by any developer on any OS. * Integration: These tests cover interactions of package components or interactions between kubernetes components and some other non-kubernetes system resource (eg: etcd). An example would be testing whether a piece of code can correctly store data to or retrieve data from etcd. Integration tests are stored in [kubernetes/test/integration/](https://git.k8s.io/kubernetes/test/integration). Running these can require the developer set up additional functionality on their development system. |