CTS – Your Technology Partner

Testing vs. Quality Assurance

Written by Jonathan Taylor on August 12, 2013

The goal of any Quality Assurance department is to have a positive influence on their IT organization with respect to process improvement, ROI and stability. To accomplish this we have to concentrate on more than just testing the product. We have to test the entire software development life cycle, not just the product. Here are some activities we often see in testing departments.

1.  Read some requirements 

2.  Create some test cases

3.  Complain that the requirements are not testable

4.  Write some design steps (not all)

5.  Complain about short testing timelines

6.  Execute the test from the requirements

7.  Complain the amount of defects

8.  Create a report or an email with some Pass / Fail metrics

This process will not create an influential QA department. This just makes QA departments the Monday Morning sport commentators. This QA team sits back, looks at some information before the game, waits for the action to happen and then points out what the loosing team did wrong.

To complete the metaphor, this QA team reads requirements instead of participating in their development. This team waits for design and development to occur instead of reviewing and scoping unit testing. Moreover, this team reports the metrics at the end of the project but does nothing with them to improve the software process.

Let’s counter this example. Let’s turn our Monday morning commentator into an assistant coach; someone that is very much in the game.

Here’s a list of what an assistant coach would do for a football game:

  1. Reviews past play and team vulnerabilities
  2. Review opponents and identify strengths and weaknesses
  3. Help create a game plan for a win
  4. Help develop practice plans
  5. Monitors practice and provides feedback to the coaching staff
  6. If needed, makes adjustments to practice and game plan
  7. Helps implement game plan during actual game
  8. Helps make adjustments during play by providing coaches with information on game play
  9. Win or lose watches tape of play to identify weaknesses
  10. Creates plan of attack for next game.

Now let’s put our QA Manager in the game:

  1. Reviews the scope of the project and it’s cost drivers
  2. Reviews SDLC and identify SDLC
  3. Help create test strategies and test plans to mitigate project and product risks
  4. Help develop requirements through static testing
  5. Monitor requirement creation for testability and scope creep
  6. If needed, work with project team members to adjust testing scope
  7. Help implement test strategy during test execution
  8. Help project team and QA team make project adjustments by providing timely execution metrics
  9. Successful project or failed project review metrics and identify areas of process improvement
  10. Change / Update product test strategies for next project. 

Monday morning commentators do very little to change the way teams play. If they are changing the play of your team, you might be getting a new coaching staff at the end of the year.

Comments

comments