Reporting on test scenarios

Once you’ve got a suite of test scenarios defined for your use cases and requirements, you’ll probably want to run some reports on that information.

Beginning in version 2012, test scenarios are no longer properties of steps or extensions, but are rather items in their own right, owned by use cases or requirements. As such, the way they get reported on has changed. Given the new structure, we've added keywords - TestScenarios, TestSteps and TestExtensions - and changed the format of how the test scenarios are reported.

Previously, it was necessary to include testing keywords within a Steps loop, in the context of a use case. Beginning with 2012, you'll need to use a TestSteps loop, within the context of a test scenario AND a use case or requirement.

See the example below, from the built-in Test Cases report template:


In this example, the $repeatUseCasesSortID loop continues after the end of the $repeatTestScenarios loop.

See the online Custom Reports User Guide (CRUG) for more information on repeats and valid contexts for the Test keywords used in a repeat. (The CRUG is also available by clicking Reports / Custom Reports on the ribbon bar.)

Have more questions? Submit a request
Was this article helpful?
0 out of 0 found this helpful


Powered by Zendesk