==== Background/Goal
Understand existing testing practices and prepare a comprehensive testing plan for AQS 2.0.
==== User stories
[] As an API Platform team member, I need to know what the testing plan is, so I my work can ladder up to the testing plan process needs.
[] As a QAT for AQS 2.0, I need to know the testing requirements and process, so AQS 2.0 can be successfully prepared for deployment.
==== Considerations
- What capabilities are critical vs nice-to-have?
- What capabilities have the biggest impact?
- What capabilities have the most dependencies?
- How can we scope this work in a way that delivers incremental benefits?
==== Requirements
[] A brief description of what the use case is
[] Bullet list of potential/expected end-user impacts (both positive and negative)
[] Bullet other internal/external impacts
[] List of what this blocks (if anything) and why. Include examples.
[] Documents links to existing artifacts, tickets, etc.
[] Open questions/additional areas to explore
**Upon completion of the above:**
[] Tech Lead & Engineering Manager review
[] Bullet list of what the related infrastructure capabilities are
[] Bullet list of potential/expected development/engineering impacts (both positive and negative)
[] Bullet list of potential/expected design impacts (both positive and negative)
[] Describe WHAT phases or chunks of work could be done and by WHO
[] List any dependencies we have on any tools, teams, etc.
[] Meeting set to review scope with Product Manager
[] Once scope completed and agreed to, next steps defined (ex: create Epic w/ subtasks)
====Acceptance criteria
[] It is clear to see how the target capability impacts end-users
[] It is clear how the target capability impacts WMF staff
[] Impact can be delivered incrementally, without having to wait months or to the end of a project to see impact
[] Non-technical audiences can understand why this work matters and how it impacts the community