diff --git a/contributors/devel/sig-testing/testing-strategy.md b/contributors/devel/sig-testing/testing-strategy.md
new file mode 100644
index 000000000..3175da4c1
--- /dev/null
+++ b/contributors/devel/sig-testing/testing-strategy.md
@@ -0,0 +1,99 @@
+## Defining a Robust Testing Strategy
+
+This document outlines a testing strategy for Kubernetes features based on the **testing pyramid**, with considerations on the existing CI system's characteristics.
+
+### The Testing Pyramid
+
+Prioritize tests based on the testing pyramid, refer to the [Testing Guide](./testing.md):
+
+- **Unit Tests:**  The foundation. Fast, isolated, and cover individual components.
+- **Integration Tests:** Verify interactions between components within your subsystem.
+- **E2E Tests:**  Test the entire system, including interactions with external dependencies. These are the most expensive and prone to flakiness.
+
+### CI Job Types
+
+The Kubernetes job uses [prow](https://prow.k8s.io) to implement the CI system. We can differentiate between different of jobs:
+
+- **Presubmit:** Runs before code is merged.
+    - **Blocking:** Prevents merging if tests fail. Use cautiously due to potential project-wide impact. We aim to have a very high bar on these jobs and ask for proof
+    of stability, reliability and performance.
+    - **Non-Blocking/Informational:** Provides feedback without blocking merges.
+- **Periodic:** Runs at scheduled intervals. Ideal for monitoring trends and catching regressions.
+- **Postsubmit:** Runs after code is merged. Useful for building artifacts.
+
+#### SIG-Release Blocking and Informing jobs
+
+SIG-release maintains two sets of jobs that decide whether the release is
+healthy: Blocking and Informing.
+
+If you are feature or area is critical for the release please follow the instructions provided in https://github.com/kubernetes/sig-release/blob/master/release-blocking-jobs.md to promote your periodic jobs to be Blocking or Informing.
+
+A condition necessary for Presubmit Blocking jobs is to be also a Release Blocking jobs.
+
+### Mitigating E2E Test Flakiness
+
+E2E tests, especially in a complex project like Kubernetes, are susceptible to flakiness due to external dependencies. To mitigate this:
+
+- **Identify Patterns:** Utilize periodic jobs and Testgrid to monitor test results and identify patterns in failures.
+- **Isolate Failures:**  Improve test isolation to minimize the impact of external factors.
+- **Retry Mechanisms:** Implement retry mechanisms in CI jobs to handle transient failures.
+It is important to differentiate clearly what are retriable errors, or you may have the risk
+of masking legit bugs that will be present in clusters running in production.
+- **Robust Infrastructure:** Ensure the test infrastructure itself is reliable and stable.
+
+###  Testing Strategy for Specific Features/Areas
+
+If your focus is on a specific feature or area within Kubernetes, consider this strategy:
+
+1. **Periodic Jobs:**
+    - Run expensive E2E tests periodically (e.g., every 6 hours).
+    - Use Testgrid to monitor trends and receive alerts for failures. This helps identify patterns and troubleshoot issues effectively.
+    - Subscribe to alerts, Testgrid provides early signals if changes elsewhere in Kubernetes break your feature.
+
+2. **Non-Blocking Presubmit Jobs:**
+    - Configure presubmit jobs to run only when specific files or folders are modified.
+    - Use OWNERS files to require approval from maintainers of the relevant codebase. This acts as a "soft block," ensuring review and accountability without the risk of halting the entire project.
+    - Encourages maintainers to take ownership of their code's quality and stability.
+
+### Example: CI Configuration
+
+```yaml
+presubmits:
+  kubernetes/my-feature:
+    - name: my-feature-e2e-tests
+      always_run: false
+      run_if_changed: 'my-feature/**/*'
+      optional: true
+      decorate: true
+      path_alias: 'kubernetes/my-feature'
+      spec:
+        containers:
+        - image: gcr.io/k8s-testimages/kubekins-e2e:v20241104-master-5917669-master
+          command:
+          - runner.sh
+          - ./test/e2e.sh
+          args:
+          - --ginkgo.focus=MyFeature
+          - --ginkgo.skip=Slow
+      annotations:
+        testgrid-dashboards: sig-my-feature
+        testgrid-tab-name: My Feature E2E Tests
+
+periodics:
+  kubernetes/my-feature:
+    - name: my-feature-periodic-e2e-tests
+      interval: 6h
+      decorate: true
+      path_alias: 'kubernetes/my-feature'
+      spec:
+        containers:
+        - image: gcr.io/k8s-testimages/kubekins-e2e:v20241104-master-5917669-master
+          command:
+          - runner.sh
+          - ./test/e2e.sh
+          args:
+          - --ginkgo.focus=MyFeature
+      annotations:
+        testgrid-dashboards: sig-my-feature
+        testgrid-tab-name: My Feature Periodic E2E Tests
+```
diff --git a/contributors/devel/sig-testing/testing.md b/contributors/devel/sig-testing/testing.md
index ca432217c..1a1a1136d 100644
--- a/contributors/devel/sig-testing/testing.md
+++ b/contributors/devel/sig-testing/testing.md
@@ -198,6 +198,11 @@ Please refer to [Integration Testing in Kubernetes](integration-tests.md).
 
 Please refer to [End-to-End Testing in Kubernetes](e2e-tests.md).
 
+## Testing Strategy
+
+Either if you are a feature owner or subsystem or area maintaner, you have to define a
+testing strategy for your area, please refer to [Defining a Robust Testing Strategy in Kubernetes](testing-strategy.md).
+
 ## Running your contribution through Kubernetes CI
 Once you open a PR, [`prow`][prow-url] runs pre-submit tests in CI. You can find more about `prow` in [kubernetes/test-infra][prow-git] and in [this blog post][prow-doc] on automation involved in testing PRs to Kubernetes.