DEV Community

Discussion on: Who Tests Code

Collapse
 
dougmckechie profile image
Douglas McKechie

In the past I have worked at companies where there was a QA team which tested our code / user stories and it was never as much of a problem as you describe.

The QA team would be involved in the project from the start and throughout attending stand ups etc, so we did not really "throw things over the wall", it was all part of the process of getting our user stories completed for the sprints.

I would say that it worked quite well and resulted in a higher quality, more "water tight" product delivered to the client as the QA testers would often test things differently to devs and find things we never thought of.

Also there was never any reduction in accountability on individual devs as all work was peer reviewed by another dev before being merged and the ticket assigned to QA, and if you did not want to have to go back and fix things that was a good incentive for doing a thorough job.

Context switching was never a problem because we would simply complete whatever user story we were currently working on and then go back to any which failed testing and fix them.

So to summarize I think having a QA team test the work was a good thing and based on my own experience at various companies in the past this worked very well.