I hope someone can shed some insights on this situation as I am not sure if I’m in the right direction.
I was asked to draft a test strategy for a project where there will be UI changes done by a vendor. Obviously, with this kind of scenario, the UAT will be done by us (the clients) based on requirements provided by our own UI/UX team.
The UI changes basically touches multiple screens (for simplicity, I have provided sample categories below):
- User management (3 screens)
- Login (2 screens)
- Payment (5 screens)
The development completion date is based on the delivery of the 3 categories above. As such, we are expecting 3 phases of UAT. I also haven’t specified the test scenarios/cases as these are just taking functionalities from our current suite (since this is just a re-skin of UI). However, I feel like this is very un-agile.
So far, I came up with the below (but I still feel like these are just information and no real action points):
Test types: (I need to put in dates)
Unit tests - to be completed by vendor
UI tests - to be completed by our UI/UX team
Functional tests (Cross-browser tests, accessibility tests, usability tests) - to be completed by QA
Performance tests - to be completed by QA
Risk areas: Payments as there are always issues in this category so lesser test coverage on User management and Login.
Automation: (I am still in two minds on this as I believe we have capacity to automate but no confidence it will be re-factored on time)
To be done post-production as selectors will change and will impact automation scripts and deadline too tight to automate during progression tests
Test approach: (I haven’t factored in no. of days for re-testing bug fixes and no agreed turnaround time for defects which sounds very waterfall if we have one)
Bugbash - QA-wide (5 resources for 1 man-day) - this means 3 man-days since there will be 3 releases
Mob testing (happy path scenarios) - involves vendor, UI/UX team, and a QA (1 man-hour with QA lead driving it)
Resources: as per above on Test approach (maybe I can group it together with Test approach)
Test data and environments