Coach package team members on end-to-end level testing
Problem
The package team builds and interacts with several components that are hard to mock for testability. We have several integration tests responsible for joining and combining parts of our application to make sure that the interaction of the parts of our component is correct, but there is a lack of tests imitating the behaviors that a user would have using our application, interacting with all the possible functionalities from the beginning to the end.
Proposal
The team owns all the test pyramid and is empowered to contribute to all the levels, including End-to-end testing. To achieve this, the SET counterpart - usually more familiar with the frameworks and tools used for this kind of testing - coaches the counterpart engineers to include end-to-end tests as part of the definition of done in a given feature.
Plan
Strategy
- The Package QA team epic reflects a set of tests identified to work on
- Risk Map mitigation plans inform the areas that are more exposed to risk and need more coverage
- Incident corrective actions warn urgent test areas to be addressed
- Code coverage analysis highlights percentual gaps on features
Pairings
Sync or async through MR/Code reviews
Issue | Milestone | MR | Rec |
---|---|---|---|
RubyGems package manager test | 13.12 | !59788 (merged) | https://youtu.be/qLkJ7UWay7s |
Add PyPI package installation test | 14.0 | !62381 (merged) | |
Improve Gradle test | 14.1 | !64419 (merged) |