Same Writer And Tester - How Do You Do it?
I was looking to get feedback on whether you have the same test case writer also execute the test cases, or does one analyst write the test cases and another execute them? Curious to know the pros and cons and what would be considered "best practice".
"Best Practice" will be linked to the context of what works for your organization and the process that you're using. The answer to your question depends on what you want to achieve. You can write the test cases and have a formal review with other team members and get different points of view into the test plan. You can write them and have someone else execute them knowing that the other person might not execute them exactly how you would.
It really all depends on what you're trying to answer with testing. Where you focus your biases or fixations and where you would like to avoid them. It also depends on the time you have to write them. You could have the case where you know where you would like to go and only have time to write high level cases as a baseline. In that case you would want to run the tests to make sure you answer the questions you set out to answer.
Depends if you have the resources. Testing generally is very lean in most organizations so you tend to get many small projects with only 1 or 2 testers assigned to a project or pigeon holes of specialty that creates situations where the same person is planning, writing, and testing the functionality. If you have the luxury of doing a 100% test execution hand-off, than that's good. It ensures you have documented the steps and have enough eyes to keep the documentation up-to-date.
Tags for this Thread