Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document about e2e how to test the specified modules #7810

Closed
wants to merge 1 commit into from
+20 −0
Closed

Document about e2e how to test the specified modules #7810

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions contributors/devel/sig-testing/e2e-tests-kubetest2.md
View file
Original file line number Diff line number Diff line change
@@ -170,6 +170,26 @@ See `kubetest2 gce --help` for more options. Note that the different
deployer and tester plugins have their own additional options, which
can be seen in their help listings.

### Testing the specified modules

Usually the entire e2e test is very time-consuming. At this time, you may only want to test the modules you are interested in or some modified tests.
You can modify the file `test/e2e/e2e_test.go` or `test/e2e/common/imports.go` like this. Comment out the modules you don't want to test, and then execute:

```sh
make WHAT=test/e2e/e2e.test
```

When the test is executed subsequently, only the tests of the imported module will be executed
For example, below the tests for the `autoscaling` and `cloud` modules are commented out so only the tests for the `common` module will be executed.

```go
import (
//_ "k8s.io/kubernetes/test/e2e/autoscaling"
//_ "k8s.io/kubernetes/test/e2e/cloud"
_ "k8s.io/kubernetes/test/e2e/common"
)
```

### Cleaning Up

During a run, pressing **Control-C** should result in an orderly