5.1 KiB
2022 Annual Report: SIG Testing
Current initiatives
-
What work did the SIG do this year that should be highlighted?
- Ginkgov2 migration
- Utilizing context provided by Ginkgo
- Test failure description improvements
- Launched prow docs site
- TestGrid API now available at testgrid-data.k8s.io
- Prow API service ("Gangway" component) merged, enabling Prow installations to programmatically trigger Prow jobs
-
What initiatives are you working on that aren't being tracked in KEPs?
- Continue to improve testing and enforcing best practices on software development
- Cost efficiency:
- Clean up orphan jobs
- Optimize existing tooling: artifact storage, log size, …
- Extend the CI to other Cloud Providers
- Development of a new TestGrid UI
-
KEP work in 2022 (v1.24, v1.25, v1.26):
- beta:
Project health
-
What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details)
-
What metrics/community health stats does your group care about and/or measure?
- Reviewers and approvers
-
Does your CONTRIBUTING.md help new contributors engage with your group specifically by pointing to activities or programs that provide useful context or allow easy participation?
- Yes! See k8s/sig-testing: Contribution and k8s/test-infra: Issue Triage.
-
If your group has special training, requirements for reviewers/approvers, or processes beyond the general contributor guide, does your CONTRIBUTING.md document those to help existing contributors grow throughout the contributor ladder?
- N/A: no special training, requirements, or processes.
-
Does the group have contributors from multiple companies/affiliations?
- Yes.
-
Are there ways end users/companies can contribute that they currently are not? If one of those ways is more full time support, what would they work on and why?
- (more reviewers, promoting active reviewers to approvers?)
- (to be filled)
Membership
- Primary slack channel member count: 2,452
- Primary mailing list member count: 407
- Primary meeting attendee count (estimated, if needed): 7-8 on average
- Primary meeting participant count (estimated, if needed): 5-6, estimate
- Unique reviewers for SIG-owned packages: 24
- Unique approvers for SIG-owned packages: 26
Include any other ways you measure group membership
Subprojects
Retired in 2022:
- k8s-gsm-tools
Continuing:
- boskos
- e2e-framework
- kind
- kubetest2
- prow
- sig-testing
- test-infra
- testing-commons
Working groups
Continuing:
- Reliability
Operational
Operational tasks in sig-governance.md:
- README.md reviewed for accuracy and updated if needed
- CONTRIBUTING.md reviewed for accuracy and updated if needed (or created if missing and your contributor steps and experience are different or more in-depth than the documentation listed in the general contributor guide and devel folder.)
- Subprojects list and linked OWNERS files in sigs.yaml reviewed for accuracy and updated if needed
- SIG leaders (chairs, tech leads, and subproject owners) in sigs.yaml are accurate and active, and updated if needed
- Meeting notes and recordings for 2022 are linked from README.md and updated/uploaded if needed
- Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - KubeCon NA 2022: SIG Testing: Intro And Updates