Create requirements

The Requirements tab of Web Runner enables you to create requirements.

In this topic:

Create requirement folders

You can create a requirement folder to group related requirements.

Create a requirement folder	To create a new requirement folder: Select the folder under which you want to create the new folder. Click New folder (), and enter a name. Alternatively, you can hover over the folder and select More Actions > New Folder.
Create a requirement folder by copy/cut	To create a requirement folder by copy/cut: Select the folder you want to copy or cut. Click Copy () or Cut (). Alternatively, you can hover over the folder and select More Actions > Copy or Cut. Select the folder where you want to add the new folder, and click Paste (). Alternatively, you can hover over the folder and select More Actions > Paste.
Rename a requirement folder	To rename a requirement folder: Hover over the folder you want to rename, and select More Actions > Rename. Enter the new name.
Delete a requirement folder	To delete a requirement folder: Select the requirement folder you want to delete and click Delete. Alternatively, you can hover over the folder and select More Actions > Delete. In the confirmation dialog box, click Yes.

Back to top

Create requirements

You can create requirements under any existing requirement folders, or create sub-requirements under any existing requirements.

To create a new requirement:

1. Select the requirement folder or requirement under which you want to create the new requirement.

2. Click New Requirement (), and enter the required information.

   Alternatively, you can hover over the folder or requirement and select More Actions > New Requirement.

   Tip: You can also create a requirement by copying or cutting an existing requirement. To copy or cut a requirement, select the requirement, click Copy or Cut, select the requirement folder where you want to add the requirement, and click Paste.

   UI Element	Description
   Name	Enter a name for the new requirement. A requirement name cannot include the following characters: \ ^ *
   Requirement Type	Select a requirement type. Available options are: Business. A business process requirement. By default, you cannot add coverage to this requirement. Folder. A folder for organizing requirements. By default, you cannot add coverage to this requirement. Functional. A system behavioral requirement. Group. A collection of related requirements. Testing. A system performance requirement. Business Model. A requirement representing a business process model entity. Undefined. An undefined requirement. You can customize the default types and create your own requirement types. For details on customizing requirement types, see Customize requirement types.
   Details tab	Displays requirement fields. Required fields are marked with asterisks.
   Attachments tab	Enables you to add attachments for the currently selected requirement.
   Rich Text tab	Enables you to enter rich formatted text for the requirement.

3. Click Submit.

Back to top

Assign requirements to releases or cycles

You can assign a requirement to releases and cycles.

To assign a requirement to releases or cycles:

From the requirements tree	From the requirements tree, hover over the requirement. Select More Actions > Assign to Release, or Assign to Cycle. In the Select Releases or Select Cycles window, select the target releases or cycles, and click OK.
From the Details tab	Open the requirement. In the Details tab, in the Target Release drop-down list, select the target releases. To assign cycles, in the Target Cycle drop-down list, select the target cycles.

Back to top

Link defects to requirements

You can link existing defects to a requirement.

To link a defect to a requirement:

1. In the Requirements tab, from the requirements tree, select the target requirement.

2. In the Linked Defects > tab, click Link Existing Defect > By ID. Enter the defect ID and click Link.

Back to top

Create test coverage

Available in versions: 17.0.1 and later

Create test coverage by linking tests to requirements. In addition to covering requirements at the level of test, you can also cover requirements by test configurations.

Coverage mode

Coverage mode indicates whether a requirement is covered by selected test configurations or all test configurations of a test.

• All Configurations. If a test, including all its test configurations, is added to coverage, the coverage mode is All Configurations.

• Selected Configurations. If selected test configurations of a test are added to coverage, the coverage mode is Selected Configurations.

To link tests to a requirement:

1. Open the requirement. Go to the Test Coverage tab.

2. Click Select to open the Test Plan tree.

3. Select the target tests and click Add to Coverage.

   To select multiple tests grouped in the same folder, select the folder and click Add To Coverage.

   To select test configurations of a test, select the test, at the bottom of the test plan tree, expand the Test Configurations section, and select target test configurations.

To remove test coverage:

From the test coverage grid, select the test coverage and click Remove .

To remove certain test configurations:

1. Change the Coverage Mode of the test coverage to Selected Configurations.

2. Expand the Test Configuration Status section, select target test configurations, and click Remove .

Back to top

Track requirement details changes

You can track the changes made to the details of a requirement.

To track requirement details changes:

1. In the Requirements tab, from the requirements tree, select the target requirement.

2. Open the History tab. By default, it displays all changes to the requirement details, grouped by change date and changer.

3. To view changes made to a specific field, from the Field drop-down list, select the field.

Back to top