diff options
| -rw-r--r-- | contributors/devel/sig-testing/testing.md | 13 |
1 files changed, 5 insertions, 8 deletions
diff --git a/contributors/devel/sig-testing/testing.md b/contributors/devel/sig-testing/testing.md index 64b4935b..99f7ba89 100644 --- a/contributors/devel/sig-testing/testing.md +++ b/contributors/devel/sig-testing/testing.md @@ -25,9 +25,6 @@ passed both unit and integration tests. Kubernetes only merges pull requests when unit, integration, and e2e tests are passing, so it is often a good idea to make sure the e2e tests work as well. - - - ## Unit tests * Unit tests should be fully hermetic @@ -279,13 +276,13 @@ It is useful as a way to: All new PRs for tests should attempt to follow these steps in order to help enable a smooth review process: -1. The problem statement should be well defined. (Describe clearly the intended -purpose of the test, and why it is needed.) +1. The problem statement should clearly describe the intended purpose of the +test and why it is needed. -2. Get some agreement on how to design test from relevant SIG. +2. Get some agreement on how to design your test from the relevant SIG. 3. Create the PR. -4. Raise awareness of your PR to respective communities. (eg. via mailing lists, -Slack channels, Github mentions) +4. Raise awareness of your PR to respective communities (eg. via mailing lists, +Slack channels, Github mentions). |