Update contributors/devel/sig-testing/testing-strategy.md

Co-authored-by: Patrick Ohly <patrick.ohly@intel.com>
This commit is contained in:
Antonio Ojea 2024-11-04 21:28:48 +00:00 committed by GitHub
parent fcd8fa11e0
commit c2c6d1b3e1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 1 deletions

View File

@ -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).