List to aid the test planning process
The Challenge
During the Test Planning process and the related conversations around quality and risks that delivers testing requirements for a feature, it is easy to miss considering areas of the product that would be impacted by the feature.
For example, this issue was caused by missed test coverage of gitlab.com plans. Only self hosted plans were covered.
Proposal
This issue proposes adding a list to aid the test planning process and drive conversations around risks. The list can be categorised based logical areas that should be considered for risk/quality assessment. Some of the areas could be obvious but should still be part of the list. It is difficult to list every potential area of consideration in one go. For the MVC, we could collaborate on the MR to agree on a few items and refine the list as we move forward.
Here is an example of potential areas:
- Authentication
- Authorization
- Business logic
- Availability in plan tiers
- Behaviour on GitLab.com vs self hosted
- ...
The list could be added as a child page under the Test Engineering Process and referred to in the Test Planning Process section.
Considerations
- How exhaustive or light weight should the list be?
- Possible implications on the time taken for the test planning process? We want to keep the test planning light weight.