Create Test Requirements actions

Create Test Requirements actions create requirements in the specified Tosca, qTest or ALM Test Repository.

Action property	Description
Pipeline	A Pipeline parameter or dataset whose Most-at-risk Gaps Test Repository provides the Test Repository in which requirements are to be created.
Result	A Table dataset that stores details of the requirements that were created.
Root Path	A String parameter or dataset that stores the name of an existing root requirements folder. If this parameter is not set, ‘Requirements’ is used as the default.
Source	A Table parameter or dataset that stores details of the requirements that are to be created.
Test Repository	A Test Repository parameter or dataset referring to the Tosca, qTest or ALM Test Repository in which to create requirements.

Tosca

For Tosca Test Repositories, the Source table should have the following columns.

Column	Description
NAME	The name of the object to be created.
PATH	The name of an existing requirements path in which the object is to be created, excluding the root ‘Requirements’ or ‘Root Path’ folder. Items in the path should be separated with a /. Requirements objects are created in the order in which they appear in the Source table.
TYPE	The type or requirement object to be created. One of: Folder RequirementSet (parented by Folder) Requirement (parented by RequirementSet or Requirement) If this column is left blank, ‘Folder’ is used as the default.
USAGE	The object’s usage count, normally obtained from the Analyze Object Links action’s Result dataset.
DEPTH	The search depth at which the object was found, normally obtained from the Analyze Object Links action’s Result dataset.

The USAGE and DEPTH values are converted automatically to Tosca requirement FREQUENCY_CLASS and DAMAGE_CLASS values (in the Tosca accepted value range). Within Tosca, a requirement’s frequency class and damage class are used to calculate the requirement’s weight as follows:

Weight = 2 ^ Frequency Class * 2 ^ Damage Class

For testable objects written to Tosca requirements by the Smart Impact app:

The Frequency Class attribute maps naturally to the object’s usage.
The Damage Class maps inversely to the object’s search depth (a low search depth represents a high Damage Class).

For Tosca Test Repositories, the Result table has the following columns.

Column	Description
REQ_ID	The unique ID of the requirement that was created (or the unique ID of an existing requirement).
NAME	The name of the requirement that was created (or the name of an existing requirement).
REQ_PATH	The path of the requirement that was created.
STATUS	This column is set to + if the requirement was created, = if the requirement already exists, or X if the requirement could not be created.

qTest

For qTest Test Repositories, the Source table should have at least the following columns.

Column

Description

NAME

The name of the object to be created.

PATH

The name of an existing requirements path in which the object is to be created, excluding the root ‘Requirements’ folder. Requirements objects are created in the order in which they appear in the Source table.

TYPE

TYPE The type or requirement object to be created. One of:

Module
Requirement (parented by Module)
TestCase (parented by Requirement)
TestStep (parented by TestCase)

If this column is left blank, ‘Module’ is used as the default.

For qTest Test Repositories, the Result table has the following columns.

Column	Description
REQ_ID	The unique ID of the requirement that was created (or the unique ID of an existing requirement).
REQ_NAME	The name of the requirement that was created (or the name of an existing requirement).
REQ_PATH	The path of the requirement that was created (or the path of an existing requirement).
STATUS	This column is set to + if the requirement was created, = if the requirement already exists, or X if the requirement could not be created.
REQ_TYPE	The type of the requirement that was created.

ALM

For ALM Test Repositories, the Source table should have at least the following columns.

Column	Description
NAME	The name of the requirement or folder to be created.
PATH	The path to the parent of a requirement record, excluding the root Requirements folder. Path components should be separated with a backslash (\). For example, MyRequirements\Phase1. If the Create Test Requirements action’s Root Path property is specified, the requirements path is created by adding the Root Path to the front of the PATH value (with a trailing \ if needed). If the Create Test Requirements action’s Pipeline property is specified, the Pipeline’s Requirements Path value is added to the front of the PATH value (with a trailing \ if needed). If the requirements path is invalid, the new requirement will not be created, and no further processing of the Source table will occur.

Column

Description

NAME

The name of the requirement or folder to be created.

PATH

The path to the parent of a requirement record, excluding the root Requirements folder. Path components should be separated with a backslash (\). For example, MyRequirements\Phase1. If the Create Test Requirements action’s Root Path property is specified, the requirements path is created by adding the Root Path to the front of the PATH value (with a trailing \ if needed).

If the Create Test Requirements action’s Pipeline property is specified, the Pipeline’s Requirements Path value is added to the front of the PATH value (with a trailing \ if needed).

If the requirements path is invalid, the new requirement will not be created, and no further processing of the Source table will occur.

The type of requirement to create is determined by the ALMRequirementType setting in the Configuration - Test Repository screen. This value may be set by a user with Administrator privileges.

For ALM Test Repositories, the Result table has the following columns.

Column	Description
REQ_ID	The unique ID of the requirement that was created (or the unique ID of an existing requirement).
REQ_NAME	The name of the requirement that was created (or the name of an existing requirement).
REQ_PATH	The path of the requirement that was created (or the path of an existing requirement).
STATUS	This column is set to + if the requirement was created, = if the requirement already exists, or X if the requirement could not be created.

Example (Pipeline)

Create Test Requirements action example (Pipeline).

Example (Test Repository)

Create Test Requirements action example (Test Repository).

Test repository integrations