September 24, 2012

Perspectives on Testing

Test Management
Welcome to Seapine’s Perspectives on Testing. Every week I’m going to look at articles, blog posts, tweets, and other testing and quality content, and provide some perspective on the news or commentary. Enjoy, and I look forward to hearing your feedback.

Agile Point of View

What it means to be done can generally be agreed upon by a single Agile team. But what happens if you have several, or many, Agile teams contributing to a single product. Johanna Rothman gives her views on how to negotiate done across teams. The definitive guide to Scrum, by Ken Schwaber and Jeff Sutherland. Acceptance Test-Driven Development (ATDD) has value in terms of focusing on business value and keeping code simpler and easier to maintain? Does this value also apply when we start automating these acceptance tests? John Ferguson Smart thinks so.

Testing Philosophy

I’ve been focusing on team communications recently, because so many things go wrong if you don’t get this right. John Mueller is also concerned about communications, and gives us 10 reasons why project teams don’t communicate. After years of reduced budgets and outsourcing, Kyle McNabb of Forrester says that software development and delivery competencies matter to an enterprise. There seems to be a general acknowledgement that we have to produce better software more quickly in order to give our enterprises a competitive advantage. What’s your take on out of scope bugs?  It really gets back to the question of the goal of testing and quality. Many years ago, I was an Air Force officer. I had to make many decisions that I felt distinctly unqualified to make. That was when I first learned to beg forgiveness, rather than ask permission. Why do you enjoy testing? Here’s Everyday QA’s perspective. Here’s what Dilbert has to say about testers. I can see everyone grinning and nodding on this one.

Seapine View

QA Wizard Pro is up for an ATI automation honors award. You can vote for your favorite functional testing solution. Linking testing artifacts to requirements is an important part of traceability. Colleague Matt Harp talks about why this is important when requirements change, and how TestTrack can help teams know what test cases are suspect due to changes.