Displaying Custom Properties at the Test Step Level

Custom Property Position

First, the custom properties (CUST_01, CUST_02, etc.) are associated according to the position they are configured for every artifact. For example, we can see below that a text field called “Additional Data” in the first position and a list field called “Step Type” in the second position. This information helps in picking the correct custom property in the ESQL query developed.

Custom Reporting for Test Steps with Custom Properties

As part of developing your custom report, add a custom section, give a name to this section, and write the following query. Preview the query results. If the result set is fine, then create the default template for this query and save the custom section added.

select R.TEST_CASE_ID, R.TEST_CASE_NAME, R.TEST_STEP_ID, R.DESCRIPTION, R.EXPECTED_RESULT, R.SAMPLE_DATA, R.CUST_01, R.CUST_02, C.NAME AS CUST_02_NAME, R.EXECUTION_STATUS_NAME AS TEST_STEP_STATUS from SpiraTestEntities.R_TestSteps as R
left join SpiraTestEntities.R_CustomListValues as C on cast (R.CUST_02 as decimal) = C.CUSTOM_PROPERTY_VALUE_ID and R.PROJECT_ID = C.PROJECT_ID
where R.PROJECT_ID = ${ProjectId}

This query brings the custom properties, CUST_01 and CUST_02, based on the positions they were added to the TEST_STEP artifact in the picture shown before. Since CUST_02 is a custom list property, the actual list value can be mapped to the custom list value data as shown in the query.

Result