You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributors/devel/sig-testing/testing.md
+30-29Lines changed: 30 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,17 +48,6 @@ passing, so it is often a good idea to make sure the e2e tests work as well.
48
48
cd kubernetes
49
49
make test# Run all unit tests.
50
50
```
51
-
If you have `GOPATH` set up correctly, you can
52
-
also just use `go test` directly.
53
-
54
-
```sh
55
-
cd kubernetes
56
-
go test ./... # Run all unit tests
57
-
```
58
-
59
-
The remainder of this documentation presumes that you use `Make` as an
60
-
entry point, but remember that the ability to use `go test` exists should you
61
-
desire.
62
51
63
52
If any unit test fails with a timeout panic (see [#1594](https://github.com/kubernetes/community/issues/1594)) on the testing package, you can increase the `KUBE_TIMEOUT` value as shown below.
64
53
@@ -80,12 +69,6 @@ added automatically to these:
80
69
make test WHAT=./pkg/kubelet # run tests for pkg/kubelet
81
70
```
82
71
83
-
Expressed strictly with `go test`, the above command is equivalent to the following:
84
-
85
-
```sh
86
-
go test ./pkg/kubelet
87
-
```
88
-
89
72
To run tests for a package and all of its subpackages, you need to append `...`
90
73
to the package path:
91
74
@@ -119,12 +102,6 @@ make test WHAT=./pkg/apis/core/validation GOFLAGS="-v" KUBE_TEST_ARGS='-run ^Tes
119
102
make test WHAT=./pkg/apis/core/validation GOFLAGS="-v" KUBE_TEST_ARGS="-run ValidatePod\|ValidateConfigMap$"
120
103
```
121
104
122
-
Or if we are using `go test` as our entry point, we could run:
123
-
124
-
```sh
125
-
go test ./pkg/apis/core/validation -v -run ^TestValidatePods$
0 commit comments