Test configuration parameter

In Tosca, test configuration parameters can be used to apply specific values to various TestCases.

These values are for instance

Test configuration parameters can be defined for various object types. Parameters are inherited hierarchically and in descending order within an object structure. Inherited values of a test configuration parameter can be overwritten for each individual object.

The value to be used as a test configuration parameter depends on the priority of the object type. For instance, an ExecutionEntry has a higher priority than the corresponding TestCase.

Test configuration parameters can be created for the objects listed below. The priority of the listed objects is from bottom to top, but parameters are inherited from top to bottom.

Business TestCase-ID for assigning identical technical TestCases (see chapter "Editing Business TestCases").

If a test configuration parameter is searched with TQL, the originally created parameter is usually found.

Creating test configuration parameters

All objects which allow configuration parameters to be created have an additional tab Test configuration in the details view.

  1. Select Create Test configuration parameter from the context menu or via the key combination Ctrl + N, Ctrl + C of the chosen object type.

    The object level where the parameter has been created is displayed in bold. Objects which inherit this parameter are displayed in the usual format.

  2. Assign a user-specific name and a value to the test configuration parameter.

Test configuration parameter

Using test configuration parameters

As soon as a test configuration parameter has been defined, it is automatically applied to some areas, for instance test data management: "Connecting with TDM repository".

In TestCases, test configuration parameters can be directly linked to in the TestStepValue using the following dynamic expression:

Syntax:

{CP[<Test configuration parameter name>]}

Specific examples on how to use test configuration parameters can be found in these chapters.

You can define the following test configuration parameters:

Test configuration parameter

Technology

Chapter

Browser

XBrowser Engine, Mobile+

"XBrowser Engine 3.0"

BusinessTypeAndroid

Mobile+

"Executing TestCases"

BusinessTypeiOS

Mobile+

"Executing TestCases"

BusyShapes

TBox

"Settings - Synchronization"

ContinuousIntegration

CI

"Preparing the Workspace"

ContinuousIntegrationBuildRootFolder

CI

"Preparing the Workspace"

CursorIdleDuration

TBox

"Settings - Synchronization"

DeviceID

Mobile+

"Executing TestCases"

DeviceType

Mobile+

"Executing TestCases"

ExampleDirectoryJSON

JSON Engine

"Structure of JSON TestCases"

ExampleDirectoryXML

XML Engine

"Structure of XML TestCases"

ExecutionType

CI

"Preparing the Workspace"

Hostname

Mobile+

"Executing TestCases"

IgnoreWhitespace

TBox

"Settings - String Operations"

MouseDelay

TBox

"Settings - Simulation"

MouseoverOffsetXAxis

TBox

"Settings - Synchronization"

MouseoverOffsetYAxis

TBox

"Settings - Synchronization"

MoveMouseOverApplication

TBox

"Settings - Synchronization"

OnDialogFailure

TBox

"Recovery"

Onlydefaultcomponents

TBox

"Settings - Extension loading"

OnVerificationFailure

TBox

"Recovery"

PageSync

TBox

"Settings - Synchronization"

SanityCheck

OSV

"Sanity check"

SendKeysDelay

TBox

"Using SendKeys"

SuppressClassicExecution

Tbox

"Running classic TestSteps with Tosca TBox"

SynchronizationTimeout

TBox

"Settings - Synchronization"

SynchronizationTimeoutDuringWaitOn

TBox

"Settings - Synchronization"

TargetDateFormat

TBox

"Generating dynamic date and time expressions"

TargetDateTimeFormat

TBox

"Generating dynamic date and time expressions"

TargetDecimalCharacter

TBox

"Number formats"

TargetGroupingCharacter

TBox

"Number formats"

TargetTimeFormat

TBox

"Generating dynamic date and time expressions"

TDMConnection

Test data management

"Test Data Management: an Example"

TestCaseRetries

TBox

"Recovery"

TestStepRetries

TBox

"Recovery"

TestStepValueRetries

TBox

"Recovery"

ToscaDateFormat

TBox

"Generating dynamic date and time expressions"

ToscaDateTimeFormat

TBox

"Generating dynamic date and time expressions"

ToscaTimeFormat

TBox

"Generating dynamic date and time expressions"

UseKeyboardLayout

TBox

"Settings - Simulation"

WaitForMobileApp

Mobile+

"Settings - Engines"

WaitingForCursor

TBox

"Settings - Synchronization"

WebserviceEngineLogLevel

Webservice Engine

"Sending and receiving messages via JMS"

WebserviceEngineLogRequestResponse

Webservice Engine

"Executing Webservice TestCases"

WebserviceEngineResponseTimeout

Webservice Engine

"Executing Webservice TestCases"

Test configuration parameters - context menu

Reset to default value

The test configuration parameter value is reset. If an inherited test configuration parameter has been adapted by the user, the value is reset to the parameter's default value (parent element). If the configuration parameter is the same as the parent element, the value will be deleted.

Copy table to clipboard

All marked test configuration parameters are copied to the clipboard as follows:

"<Parameter name 1>" "<Value>"

"<Parameter name 2>" "<Value>"

Translate Value

see also chapter "Verifying dynamic values"

Test configuration parameters in TestCase logs

Any used test configuration parameters are shown as TestCase logs.

Example: file paths

A straightforward example for test configuration parameters is the definition of program paths in various operating systems. If a test should be executed using both Windows XP and Windows 7, then various program paths must be stored.

Procedure

  1. Create the test configuration parameter Progpath for TestCase Test 3 in the TestCases section.

  2. Use the syntax C:\{CP[Progpath]}\TRICENTIS in the TestStepValue to link this with the configuration parameter Progpath.

Example for test configuration parameter

  1. Use TestCase Test 3 to create ExecutionLists for every operating system in the ExecutionLists section.

    The test configuration parameter is copied to the ExecutionLists.

  2. In the next step, define the paths of the respective operating systems as values for the test configuration parameters.

Configuration parameter in the ExecutionList


FEEDBACK

Was the information helpful?

© by Tricentis GmbH