Agile Testing-5 Steps to QA Adaptation

[article]
Member Submitted
  • case(s). QA engineers will have either created or updated existing workflow test cases from their test case abstracts. The preference, if possible, is to update existing workflows so our existing test library is always up to date.
  • Generally, this is a 1 hour meeting which occurs within one to five days after the first step in the QA methodology. Additional meetings might be required to review all test cases.

Outcome

  •  A holistic workflow that reflects the persona(s) of an actual application user.

Test Execution
Problem

  • Generally, the testing efforts are at risk when new features are not fully understood, features are delivered late, or the test execution is delayed or rushed.

Purpose

  • The purpose of this task is for the QA team to review the test execution progress by:
  1. collaboratively discussing the areas that have been tested and not tested,
  2. review heuristic and exploratory testing opportunities,
  3. identify any testing gaps (ad hoc application changes),
  4. assess automated regression testing, and
  5. extending the knowledge distribution within the team

Process, Timing and Frequency

  • During the QA test cycle the QA team shares and reviews the progress of their (1) workflow test execution, and (2) identify any test execution obstacles or serious defects.
  • Generally, this is a 1 hour meeting which occurs usually one day after each build is deployed to the QA environment.

Outcome

  • Assessment of the testing progress, as well as, identifying obstacles that interfere with the testing phase.

Test Run Check Points
Problem

  • Producing status reports reduces valuable testing time from each QA engineer, implementing developer or product management test case reviews also reduces their time to address code or design flaws.

Purpose

  • The purpose of this task is for the QA team to take ownership for the testing progress at both the feature (functionality) and workflow levels.
  1. Report on the areas that have been tested and not tested,
  2. Report any major obstacles that prevent/block testing,
  3. Re-prioritize or shuffle testing efforts,
  4. Escalate issues to development and/or product management,
  5. Create awareness within the team to (a) reduce duplicated testing efforts, and (b) reduce duplicated issues reported in the defect tracking system, and
  6. Address automated regression scripts.

Process, Timing and Frequency

  • During the QA test cycle the QA team shares and reviews the progress of their (1) workflow test execution, and (2) identify any test execution obstacles.
  • Generally, this is a 1 hour meeting which occurs usually one day after the 1st build, at the mid-point of the testing phase, and daily during the last week in the QA cycle.

Outcome

  • Continual testing progress assessment, prioritization of test efforts, and a method to address to obstacles in the testing phase.

Our Agile QA Adaptation has been put into practice and has proven itself with low production defects (averaging less than 3% of production issues are defects). Whether you have local or remote teams, the QA Agile Adapation works nicely to help you gain a better understanding of each person's aptitude in your application, and supports new staff members by leveraging the knowledge of each person on the team.

About the author

Reginald Tirona's picture Reginald Tirona

Reginald Tirona has over 10 years of experiences in directing and managing QA organizations at various companies from start-ups to mature corporations. His insight and agile approach to QA strategies have shown proven results in increasing testing coverage, reducing escape rates, and meeting both engineering-centric and customer-centric goals.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!