Specify manual Test Steps

You can optionally define discrete Test Steps in Test Cases.

The advantage of this approach is threefold:

  • Any failure can be linked and easily traced to the test step in which it occurred.

  • Test Steps data is separated from the Description field, which can be then reserved for general information about the Test Case.

  • If a Test Run is exported to Excel for manual execution of tests offline, only test step and results data are involved in the round-trip. Other Test Case data, such as the Description, cannot be modified by external testers.

Specify manual Test Steps in the Classic Execution view

You can switch back to the classic execution view method described below by entering the following property in the Properties section.

testManagement.useOldExecutionView=true 
Warning:

To give current testers some time to transition to the new Test Execution View workflow, we will still support the Classic Test Execution View for a few more releases. Recommendation: Get to know the improved workflow outlined in the Executing a Test Run Using Polarion section.

Your project administrator can then enable the specification of manual test steps in the project configuration.

(See Enabling Manual Test Steps.)

When correctly configured, a table of test steps appears in the Custom Fields section of new Test Case items (unless the administrator opted to display the table separately). Testers can specify each test step as a row in the Test Steps table. The table is rendered as executable test steps in a panel in the Execute Test Case section of the Test Case Work Item when the Test Case is executed during a Test Run. As shown below, Testers can log the results of individual test steps.

Reuse recent results.