Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
QA Role
This page should help the solution sales team to know more about QA Analyst role and identify how much it is needed on the project.
...
Some expectations from the customers are more misunderstandings of the role QA Analyst - please check truths and myths section on our Confluence /wiki/spaces/CUST/pages/1932329897
Advantage of QAs on projects
The main reasons why to have QA Analyst on the project are:
Benefits for the customer
the customer is responsible for performing UAT testing - full support of QA Analyst will help the customer be prepared for this project phase
the QA Analyst can share our best practices from our projects with the customer - documents and presentations for this are ready (how to create test cases, how to organize UAT, how to report bugs). The QA Analyst is ready to discuss those things with the customer and help them if they don’t have big experience with software testing.
the QA Analyst is the role dedicated for discussing testing related issues with the customer
the QA Analyst can do the software demo for the customer
Benefits for our project team
QA Analyst will lower the risk the customer will find a bug during his testing
QA Analyst is the role dedicated for testing the solution - CE is a developer, he will not prepare test strategy and test cases, he can test but his time for testing will be always limited because testing is not his main job. So usually you can’t expect CE will test the solution the same way as QA Analyst.
QA Analyst can lower the probability the customer will not be ready for UAT testing and we will discover this too late.
QA tasks and responsibilities
The following activities can be done by QA Analyst - if there is no QA Analyst on the project, they need to be done by CE, SA or PM
...