diff options
| author | Caleb Woodbine <caleb@ii.coop> | 2019-10-02 09:46:45 +1300 |
|---|---|---|
| committer | Caleb Woodbine <caleb@ii.coop> | 2019-10-02 09:46:45 +1300 |
| commit | 2aa77f1a77fede208da50053a50db3e02aaca0d8 (patch) | |
| tree | 608a453dff84d876ff1a46375fcccd98a5fa66b8 | |
| parent | 3294528633ce00e3ee932b2e638d7f4d4592556b (diff) | |
Add clean up docs
| -rw-r--r-- | contributors/devel/sig-testing/writing-good-e2e-tests.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/contributors/devel/sig-testing/writing-good-e2e-tests.md b/contributors/devel/sig-testing/writing-good-e2e-tests.md index ee82a197..39727ea5 100644 --- a/contributors/devel/sig-testing/writing-good-e2e-tests.md +++ b/contributors/devel/sig-testing/writing-good-e2e-tests.md @@ -236,9 +236,11 @@ Therefore it is important to use resources that are: 1. appropriate to the test 2. inexpensive (containing little or no overhead) 3. create just as many an needed, no more +4. should be cleaned up at the end of the tests's run For example: 1. only using the resource type which is appropriate to the `test/e2e/<AREA>/<SPECIFIC_AREA>` 2. the resource type `ConfigMap` is inexpensive, common, and stateless. It should be used for such things as fetching created resources 3. although the clusters used for testing are generally beefy, an overamount of resources should not be created as it is unnecessary +4. using afterEach, make sure that your test destroys any resources leftover from the test |