Manage Requirements

In Testsigma, each test case can be mapped to a requirement. This helps you organize your testing by addressing each individual software requirement.

Prerequisites

1. This document assumes that you know how to create a test case. If not, refer to Create test case.
2. Requirement types.

Navigation

Select Project > Test Development > Requirements

Create a Requirement

 1. Navigate to a specific project
 2. Within the project, navigate to the Test Development menu
 3. Click on the Requirements menu as shown in the screenshot below:

 4. Within the requirements page, click on the ‘create’ button in the top right corner.
 5. The ‘Create Requirements’ page will appear as also shown in the screenshot below:

You will see below options on the form:

• Name
  
• Description(optional)
  
• Type: Choose one of the options. The options will get populated from the requirement types page
  
• Start Date: When should the testing for the requirement start?
  
• Completion Date: When should the testing for the requirement end?
  
• Planned Manual Count: How many manual test cases should be part of this requirement?
  
• Planned Automation Count: How many automated test cases should be part of this requirement?
  
  

 6. Click on the ‘Create’ button.

Here’s a sample requirement:

Edit a Requirement

Hover over a requirement on the ‘Requirements’ page and click on the ‘Edit’ button, also highlighted in the screenshot below:

Delete a Requirement

Hover over a requirement on the ‘Requirements’ page and click on the ‘Delete’ button, also highlighted in the screenshot below:

Associate a Requirement to a Test Case

1. While creating a test case, a click on the advanced options menu, choose the requirement you created in step 2

According to IEEE standard 729, a requirement is defined as follows:

• A condition or capability needed by a user to solve a problem or achieve an objective
• A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally imposed documents
• A documented representation of a condition or capability as in 1 and 2

A software requirement can be of 3 types:

• Functional requirements
• Non-functional requirements
• Domain requirements