Versions Compared

Old Version 2

changes.mady.by.user Support Advocate (ease solutions)

Saved on

compared with

New Version 3

changes.mady.by.user Support Advocate (ease solutions)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
titleContents

Table of Contents

Panel

Properties

Parameter KeyThe key that identifies the parameter.
It's required and has to be set during the creation of the parameter. It can be edited later.
The names for parameters of the same test have to be unique. 
IdentifierThe identifier to use the parameter in test steps of the corresponding test.
The identifier is automatically generated from the parameter key and is always of the following form: ##parameterKey## 
The identifier can be used within the name, description or expected result of test steps of the same test.
Occurences of the identifier will be replaced with the value of the corresponding parameter during execution. 
ValueThe value of a parameter.
It's required and has to be set during the creation of the parameter. It can be edited later.
The value can be overwritten for specific test plans or single test executions. 
Panel

Views

Issue Detail View

The issue detail view of a test can be reached by selecting the test in the definition tree of a project.
The Parameters section of the issue detail view displays all parameters of the corresponding test.

Displayed properties for each parameter:

  • Parameter Key
  • Identifier
  • Value 

If parameters are used within test steps the identifier is part of the name, description or expected result.
Therefore the identifier will be displayed in the Test Steps section of the issue detail view within those values.
Note that during the test definition the identifiers are displayed not the values of the parameters. The replacement happens only during the execution. 

Test Execution

A single test execution can be started from the definition tree or plan tree via context menu of a test.
A test plan can be executed via context menu in the plan tree or via execution view.

If parameters were used in test steps that are part of the execution, the execution runner will display the (overwritten) value instead of the identifier. 

...