It is expected that partners will have their own QA Analysts in the project team, but it doesn’t mean we can’t offer help them. We can help especially in these areas:
meeting at the beginning of the project - during planning or at the beginning of Feature Sprints
clarify expectations from testing
discussion about responsibilities during Feature Sprints and during UAT
check that Partner is ready for testing on the project
clarify potential risks so Partner knows about what can happen when testing is not done
expectation from test management tool usage
beginning of the project
clarify expectations from QA Analyst
tools and methodology
UAT phase and project ending
testing by customer
potential risks
sharing our project experiences
typical issues during projects
importance of testing
tips for smooth projects
tips for QA (/wiki/spaces/CUST/pages/4276486153 )
allocation
cooperation with other roles and with the customer
expectations during project phases
test management (/wiki/spaces/CUST/pages/4269965388)
tool selection
test cases
bug reporting
sharing test management with customer during UAT
test automation (/wiki/spaces/CUST/pages/4275929238 )
demo of Cypress
tips for usage
communication with customer
testing during Feature Sprints
UAT testing (/wiki/spaces/CUST/pages/4322099311 )
Upgrade testing (/wiki/spaces/CUST/pages/4430004299 )
bug reporting (/wiki/spaces/CUST/pages/2034565330 )
E2E test cases (template is on SP: https://pricefx.sharepoint.com/sites/PFX/Customer%20Solution/Forms/AllItems.aspx?newTargetListUrl=%2Fsites%2FPFX%2FCustomer%20Solution&viewpath=%2Fsites%2FPFX%2FCustomer%20Solution%2FForms%2FAllItems%2Easpx&id=%2Fsites%2FPFX%2FCustomer%20Solution%2F30%20Customer%20Solutions%2FCompetencies%2FQA%2FTemplates&viewid=60a4c9d9%2D575b%2D4ee2%2D8a7e%2D09776e8f55b8 - “UAT end to end test cases” file)