Filter Test Cases actions

Filter Test Cases actions filter test cases returned by the Search Test Repository action to find the test cases that match the test data returned by the Create Object Differences Report action. The results are stored in a Table dataset. Filter Test Cases actions support qTest, SAP Solution Manager and Tosca Test Repositories.

Action property Description
Filter A Table parameter or dataset containing the test data to be used for the filter. This should normally be set to the TestData dataset returned by the Create Object Differences Report action.
Pipeline A Pipeline parameter or dataset whose Most-at-risk Hits Execution Test Repository provides the Test Repository for which the test cases are to be filtered.
Result A Table dataset that stores the matching test cases. For Tosca Test Repositories, the Result dataset will be empty if either the Filter or Source dataset is empty.
Source A Table dataset containing the qTest, SAP Solution Manager or Tosca test cases to be filtered. This should normally be set to the Result dataset returned by the Search Test Repository action.
Test Repository

A Test Repository parameter or dataset that is linked to the Test Repository for which the test executions are to be filtered. If both a Test Repository and Pipeline are specified, the action uses the specified Test Repository only.

The Filter table should have the following columns:

Column Description
TABLE_NAME The name of a table containing a key/value pair to be matched against the test cases.
KEY_FIELD_NAME The name of the key field.
KEY_FIELD_VALUE The key field value.

The Source table should have the following columns, returned in the Search Test Repository action’s Result dataset.

Column Description
TEST_REPOSITORY The name of the Test Repository that was searched.
TEST_REPOSITORY_TYPE The type of the Test Repository that was searched.
NAME The matching token from the Source table’s NAME column.
TEST_ID The ID of a matching test asset.
CONFIDENCE

For each NAME in the Source table, this column stores the percentage of SEARCH_TERM values for which a matching test asset was found. If a technical name is matched in a test, the NAME’s CONFIDENCE value is set to 100. This column is populated for Tosca, qTest, ALM and SAP Solution Manager Test Repositories only.

COMMON_TERMS A list of the all the SEARCH_TERMS matched in the test asset. This column is populated for Tosca, qTest, ALM and SAP Solution Manager Test Repositories only.
TEST_NAME The name of the test asset.
TEST_PATH The test asset’s path. Note that if a matched token contains path separators, these will be escaped and stored as \/ in the test path.
TEST_URL The test asset’s URL.
WORKSTATE For Tosca Test Repositories, this column is set to the workstate associated with the test asset.
RANK The test’s rank, either H (High), M (Medium) or L (Low), based on how recently it was last run, its passes and fails, the number of runs per day, and the number of test steps. More highly ranked tests should be prioritized over tests with a lower rank.

The Result dataset has the following columns:

Column Description
TEST_REPOSITORY The name of the Test Repository that was searched.
TEST_REPOSITORY_TYPE The type of the Test Repository that was searched.
TEST_ID The ID of a matching test case from the Source table.
TEST_NAME The name of the matching test case.
TABLE_NAME The name of the table whose data was found in the test case
KEY_FIELD_NAME The KEY_FIELD_NAME that was matched from the Filter table.
KEY_FIELD_VALUE The KEY_FIELD_VALUE that was matched from the Filter table.
TEST_PATH The matching test case’s path in the specified Test Repository.

Example (Pipeline)

Filter Test Cases action example (Pipeline).

Example (Test Repository)

Filter Test Cases action example (Test Repository).

Related topics

Create Object Differences Report actions

Search Test Repository actions

Test repository integrations