Cover Requirements Actions
In the normal course of testing tool usage, it is common for test assets to be created but not linked to requirements. If left unchecked, the requirements and test modules in the project can quickly become out of sync. The Cover Requirements action may be used to keep the modules synchronized by automatically linking test assets with requirements.
The Cover Requirements action works by matching the name of the requirements with any number of test asset characteristics. For example, you could match requirement names with test names, any of the design step attributes, or a custom property. The rule for covering is that some test value must completely contain all the words of the requirement. Unattached tests are not processed by the action.
| Action Property | Description |
|---|---|
|
Cover Mode |
A String parameter which determines how requirements are matched to test assets. If the parameter is set to ‘Default’ or left unset, requirements and tests are matched based upon similar names. If the parameter is set to ‘Source’, the action uses the Source table to link test plans with requirements directly. |
|
Fields To Search |
A String List parameter or dataset containing a list of database fields to search. If this property is not set, all fields will be searched. Setting the Fields To Search property appropriately can significantly reduce the time it takes to search for relevant test assets. You must use the database column names and not the project entity field names. For example, to limit the search to the test plan ‘Name’ field, you should use TS_NAME. |
|
Include Req Paths |
A String List parameter or dataset containing a list of requirement paths to search when identifying requirements to cover. For example, Requirements\Phase1. Each path and all its descendants are searched. If this parameter is not set, all requirement paths in the specified Test Repository will be searched. |
|
Include Test Paths |
A String List parameter or dataset containing a list of test paths to search when identifying requirements to cover. For example, Subject\Master. Each path and all its descendants are searched. If this parameter is not set, all test paths in the specified Test Repository will be searched. |
|
Result |
A Table dataset containing a list of the requirements covered, and their test assets. |
|
Source |
A Table parameter or dataset which is used to link test plans and requirements. This property should only be set if the Cover Mode property is set to ‘Source’. |
| TestRepository | A Test Repository parameter or dataset referring to the Test Repository in which to cover requirements. |
Examples:
Cover Mode = Default
Cover Mode = Source
If the Cover Mode parameter is set to ‘Source’, the Source parameter should be set to a table with the following columns:
| Column | Description |
|---|---|
|
TEST_PLAN_ID |
The ID of a test plan. |
|
REQ_NAME |
The name of a requirement to be associated with the test plan. |
The Result dataset has the following columns:
| Column | Description |
|---|---|
|
REQ_ID |
The ID of a requirement that was covered. |
|
REQ_NAME |
The name of the requirement. |
|
TEST_ID |
The ID of a test that was associated with the requirement. |
|
TEST_NAME |
The name of the test. |
|
TEST_MATCH_VALUE |
The string value that matched the requirement with the test. |