Reviewing Requirements and Capturing Questions QA Analyst Training PART06 Hands-on Training Reviewing Requirements and Capturing Questions To protect the confidential and proprietary information included in this material, it may not be disclosed or provided to any third parties without the approval of QA TRAING EXPERTS.

Test Planning Test Planning Activities  Defining the Testing Strategy  Reviewing Requirements and Capturing Questions  The Requirement Walkthrough  Capturing Requirements in an RTM Test Planning

Reviewing Requirements and Capturing Questions Activity: Reviewing Requirements and Capturing Questions When: Before The Requirement Walkthrough Responsible: Test Team, Test Lead

Reviewing Requirements and Capturing Questions Business requirements Technical requirements

Reviewing Requirements and Capturing Questions  The Query Log or Query Tracker Purpose: To capture the questions from QA on the requirements.

Reviewing Requirements and Capturing Questions In order for QA to validate the requirements we must understand them. Requirements are not easy to understand at first glance. Understanding the requirements is not our only goal during the review process.

Reviewing Requirements and Capturing Questions Tasks that are performed: Requirements are handed off to the QA Team once finalized. Each Team member reviews the requirements to gain as much of an understanding of them as possible. Questions are captured from the QA Test Team using a Query Log or Query Tracker to be reviewed during the Requirement Walk through meeting.

Reviewing Requirements and Capturing Questions Understand the requirements as much as possible. To identify requirements that do not contain enough information, ones that we need clarify one, appear to be missing information, or requirements are not complete. To identify requirements that are ”not testable” as well as anything else that should be listed as “Out of Scope” in the Test Plan.

nd Capturing Questions QA should never assume anything about a requirement. Requirements are not always defined with enough detail. Requirements must be specific so they are testable. Understanding the requirements is critical to your success and the project’s success. If the requirement is wrong then the code will be wrong and our test will test it wrong.

Reviewing Requirements and Capturing Questions Important Tips: First from a high level review the entire document to understand how the requirements are structured in the document. Read each requirement slowly… take your time. Breaking it down into small pieces to help understand it. Look for key words… highlight the keywords. Ask yourself… “How would I test this?”

Reviewing Requirements and Capturing Questions Most Important Tip of all: Do not get discouraged if you don’t understand the requirements at first glance. This is typical even for the tester with over 10 years of experience. The purpose of QA is to approach the requirements and the testing of them with a fresh eyes.

Things To Look For CLEAR AND CONCISE Are the requirements clear and understandable? some things to think about and look for: Here are Can it only be understood one way? Stated simply Concise

Things To Look For FREE FROM AMBIGUITIES Are requirements free of ambiguities? An ambiguity is an expression whose meaning cannot be determined from its context . Examples of words that should not be used: as appropriate etc. and/or

Things To Look For INCOMPLETE REQUIREMENTS Are the requirements complete and free from any remarks like TBD, pending, To follow up, etc. Often these are overlooked by the writer and missed. You always want to be sure it’s a simple matter a missed deletion or is it a requirement that requires further work to finalize it.

Things To Look For IS IT TESTABLE? Some requirements captured may not be testable. These are identified and listed as out of scope in the Test Plan. Can the requirement be validated? Is it testable? Can you identify the criteria to verify it? Does a means exist to measure and/or check the requirement?

Examining Test Requirements

Test Planning Test Planning Activities  Defining the Testing Strategy  Reviewing Requirements and Capturing Questions  The Requirement Walkthrough  Capturing Requirements in an RTM Test Planning