From c2c6d1b3e1c073eb5f3eaf1d70c7e9427fdda380 Mon Sep 17 00:00:00 2001 From: Antonio Ojea Date: Mon, 4 Nov 2024 21:28:48 +0000 Subject: [PATCH] Update contributors/devel/sig-testing/testing-strategy.md Co-authored-by: Patrick Ohly --- contributors/devel/sig-testing/testing-strategy.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/contributors/devel/sig-testing/testing-strategy.md b/contributors/devel/sig-testing/testing-strategy.md index 6747bf316..b9b786589 100644 --- a/contributors/devel/sig-testing/testing-strategy.md +++ b/contributors/devel/sig-testing/testing-strategy.md @@ -47,7 +47,12 @@ of masking legit bugs that will be present in clusters running in production. ### Testing Strategy for Specific Features/Areas -If your focus is on a specific feature or area within Kubernetes, consider this strategy: +If your focus is on a specific feature or area within Kubernetes, it is your responsibility +to ensure that tests for that a) run in the CI and b) remain healthy. +SIG Testing provides the *tooling* for running tests, but is not +responsible for *running* specific tests. + + Consider this strategy: 1. **Periodic Jobs:** - Run expensive E2E tests periodically (e.g., every 6 hours).