Tutorial 2: Define Requirements & Risks

Quantify quality metrics.

Introduction

After you create a project, it's time to define your organization’s quality metrics by specifying requirements and risks. These measures support your filter options at each stage of the testing process.

Requirements define project stakeholder needs. They validate test results and make sure project outcomes align with business objectives. Risks define project hazards that can direct your testing efforts.

Each project comes with its own set of requirements and risks.

Requirements and risks are defined at project start-up because they play an essential role throughout the total test process. Link requirements and risks to test cases because they support filter option selection during test set up. Because test cases, test results, and issues are interconnected, you can create extensive reports based on these quality metrics. 

Set up

Start defining requirements and risks by clicking Define > Requirements or Define > Risks in the header.

Clicking the links opens an overview page that displays a list of defined requirements or risks for the active project.

Adding a requirement

Add a requirement by clicking the Add Requirement button in the top right corner of the Requirements overview page.

A pop-up box displays. Fill in the data fields:

  • Type (optional)

  • Name (required)

  • Description (optional)

  • Tags (optional)

Click Save to add the requirement.

Adding a risk

Add a risk by clicking the Add Risk button in the top right corner of the Risks overview page.

A pop-up box displays. Fill in the data fields:

  • Classification (optional)

  • Name (required)

  • Description (optional)

  • Tags (optional)

Click Save to add the risk.

 

Next tutorial

>> Tutorial 3: Test Case Design