Is it a common practice to have one QA Analyst write test cases and then have others execute them? As opposed to writing and executing being done by the same person.
It depends. There are good points to doing that, interdependence, four-eyes, neutrality, knowledge-spread, and bad points time-cost, misinterpretation, knowledge-leaking, reduced ownership. Why do you ask, and what do you do at the moment?
Most places I've worked the same person generally does both but there is often some crossover between what people do.
My team write cases with the aim of each person running their own, but knowing that anyone with knowledge of the system will be able to run their test cases. They may not do it in exactly the same way, but that's fine by me, the more diverse the better as far as I'm concerned.
I've seen situations where analysts write the tests and hand them over to the testers, it hasn't worked too well, the tester is just too far removed form the business requirements to be anything other than someone driving a keyboard. The test case has to be in such detail, because the tester doesn't really see the whole picture, that you may as well automate it.
Everywhere's within walking distance if you have enough time.
Hi, thank you for you reply. Well we used to have the same tester create and execute the test cases but have moved to having a different tester write and execute. To me it seems like as someone else here mentioned in many cases the tester is too removed from the requirement to understand what is being tested.
Pretty common practice these days to have on-shore resources writing tests and off-shore folks doing the regression execution. And even all in house if the team is large enough it's bound to happen naturally as resources shift and the project ages. Have also seen setups where there is a lead that writes tests for a certain functionality and they have executors under them on the team that run and maintain the tests.
Last edited by NoUse4aName; 11-28-2012 at 10:24 AM.