You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributors/devel/sig-testing/testing-strategy.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ This document outlines a testing strategy for Kubernetes features based on the *
7
7
Prioritize tests based on the testing pyramid, refer to the [Testing Guide](./testing.md):
8
8
9
9
-**Unit Tests:** The foundation. Fast, isolated, and cover individual components.
10
-
-**Integration Tests:** Verify interactions between components within your subsystem.
10
+
-**Integration Tests:** Verify interactions between components within your subsystem. These are preferred for tests which require cluster components to be run with test-specific configurations.
11
11
-**E2E Tests:** Test the entire system, including interactions with external dependencies. These are the most expensive and prone to flakiness.
0 commit comments