Growth/Team/QS Lead Support
When to Seek for QS Support
[edit]Most day to day tickets can be tested within the team by the Product Manager, Designer, Engineers and Engineering Manager on a team. In order to make the best use of the assigned QS Lead's time on the team, it would be ideal for tickets to meet a certain threshold for them to be considered worthy of their involvement.
A ticket would qualify for QS Lead support if it meets any of the criteria below:
- An epic or tracking task with multiple Acceptance Criteria's(AC1, AC2, ...) or User Stories(Given..., When..., Then.. statement) which relates to an experiment release. Consider asking the QS lead on how to setup an integration test to catch regressions in future.
- A task that could be affected by a combination of MediaWiki settings on a particular wiki("Matrix of doom" tasks).
- A task that is touching on a known and well documented problem area in the extension.
- A task that requires special permissions i.e. IP Blocking to reproduce on production.
Ensure that the Phabricator ticket is in the "QA" column and has all the relevant information such as a clear acceptance criteria and QA notes that the QS would need to inform their testing approach.