Skip to content
This repository was archived by the owner on Jul 30, 2021. It is now read-only.

Commit 8c7fd7f

Browse files
author
Patrick Baxter
committed
update README.md with new test cmds
1 parent cc47f58 commit 8c7fd7f

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -111,11 +111,12 @@ make install
111111
Running `make run-single` or `make run-multi` resets the single-node or multi-node Vagrant environments, respectively, in the background while compiling bootkube and provisions the fresh VM with bootkube when compilation is complete. This is intended to speed up iteration.
112112

113113
## Running PR Tests
114-
The basic test suite should run automatically on PRs. It can be re-run by commenting to the PR: `rktbot run tests`. To whitelist an external contributor's PR temporarily, one can use the `ok to test` command.
114+
The basic test suite should run automatically on PRs. It can be re-run by commenting to the PR: `rktbot run e2e`. To whitelist an external contributor's PR temporarily, one can use the `ok to test` command.
115115

116-
More extensive self-hosted etcd testing can be run by commenting: `rktbot run etcd tests`. The maintainers will be responsible for determining if this is needed and should pass as it may contain experimental or flaky tests.
116+
If changes are made to the checkpointer code you manually trigger tests to run via: `rktbot run e2e checkpointer`. This builds the checkpointer image from the repo and includes that image into the test bootkube binary being built. All the same tests are run.
117117

118-
If changes are made to the checkpointer code you must run a third type of test: `rktbot run checkpointer tests`
118+
## Running conformace tests on PRs
119+
Commenting `rktbot run conformance` will trigger conformance tests against that PR.
119120

120121
## Conformance Tests
121122

0 commit comments

Comments
 (0)