Interested in how we can most effectively test Kubernetes. We’re interested specifically in making it easier for the community to run tests and contribute test results, to ensure Kubernetes is stable across a variety of cluster configurations and cloud providers.
The Chairs of the SIG run operations and processes governing the SIG.
The following subprojects are owned by sig-testing: - test-infra - Owners: - https://raw.githubusercontent.com/kubernetes/test-infra/master/OWNERS - repo-publishing - Owners: - https://raw.githubusercontent.com/kubernetes/publishing-bot/master/OWNERS - testing-commons - Description: The Testing Commons is a subproject within the Kubernetes sig-testing community interested code structure, layout, and execution of common test code used throughout the kubernetes project. - Owners: - https://raw.githubusercontent.com/kubernetes-sig-testing/frameworks/master/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/test/OWNERS - Meetings: - Testing Commons: Wednesdays at 07:30 PT (Pacific Time) (bi-weekly). Convert to your timezone. - Meeting notes and Agenda.
The below teams can be mentioned on issues and PRs in order to get attention from the right people. Note that the links to display team membership will only work if you are a member of the org.
The google groups contain the archive of Github team notifications. Mentioning a team on Github will CC its group. Monitor these for Github activity if you are not a member of the team.
|Team Name||Details||Google Groups||Description|
|@kubernetes/sig-testing-api-reviews||link||link||API Changes and Reviews|
|@kubernetes/sig-testing-bugs||link||link||Bug Triage and Troubleshooting|
|@kubernetes/sig-testing-test-failures||link||link||Test Failures and Triage|