DevOps Zone is brought to you in partnership with:

Benjamin is an independent agile consultant and developer from London, currently working on Devops related projects in the banking and finance industry. He is the maintainer of the DevOps Friday mailing list (www.devopsfriday.com). Ben is a DZone MVB and is not an employee of DZone and has posted 14 posts at DZone. You can read more from them at their website. View Full User Profile

Where Development Meets QA

06.30.2012
| 5867 views |
  • submit to reddit

In the software world, development and QA are often organised into two separate teams.

Developers are responsible for writing the code, which they’ll periodically ‘pass over the wall’ for testers.

Testers will then test the software and raise issues in some bug tracking system and pass them back to developers to fix.

Some issues may bounce between the teams multiple times before they reach resolution and the release can ship.

As a developer, this has always struck me a hugely inefficient workflow. It’s full of communication overhead, liable to miscommunication, and crucially, allows developers to fall into bad habits as they begin to rely on a seperate team being responsible for quality.

As discussed elsewhere on the site, I advocate developers being responsible for testing both their own code and testing of the application quality as a whole.

However, if you do have seperate development and QA on staff, and are either adopting agile or simply want to work more efficiently, one of the most important changes you can make is to get your developers and QA teams working much closely together.

Published at DZone with permission of Ben Wootton, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Tags: