kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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

Co-authored-by: Jordan Liggitt <jordan@liggitt.net>
This commit is contained in:
Antonio Ojea 2024-11-04 21:35:51 +00:00 committed by GitHub
parent b560706838
commit cdd1826b0e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contributors/devel/sig-testing/testing-strategy.md
View File

@ -6,7 +6,7 @@ This document outlines a testing strategy for Kubernetes features based on the *
Prioritize tests based on the testing pyramid, refer to the [Testing Guide](./testing.md):
- **Unit Tests:** The foundation. Fast, isolated, and cover individual components.
- **Unit Tests:** The foundation. Fast (a package *should* be able to run all its unit tests in seconds), isolated (doesn't depend on environment or non-local network), and cover individual components.
- **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.
- **E2E Tests:** Test the entire system, including interactions with external dependencies. These are the most expensive and prone to flakiness. Every cluster component configuration variant requires a distinct e2e job.