| || |
Should the BA help or do the testing strategy?
We have a number of projects where we utilise developers and QA.
In a number of cases, QA (offshore) doesn't always fully understand the software so I feel it might be necessary for a BA to supplu them with test cases, scenarios, etc.
But how can they do the QA properly if they don't understand the changes/buisness? How can they do the regression testing without understanding the entire data chain?
Normally speaking, I don't think the BA should do the test cases, that's the job of QA and UAT. All the BA has to do is specify the acceptance criteria and talk that through with QA and validate/approve it.
I don't think the BA team should test or write the test cases. That is QA's job. Though the BA can help test the basics I guess, but the main testing is QA. If they do not understand the specs, they need to get with the BA to understand them so they can write solid test cases. Also, UAT is great, but they should only execute the test cases, not write them. That has been my experience anyway.