Scenario Settings

Scenario Settings stores the description, default input values, runtime behavior, and D2D device roles that belong to the scenario itself.

After creating a scenario and adding steps, check Scenario Settings before running the scenario.
Setting defaults and runtime conditions first makes the run result easier to review.

This page covers settings saved in Stego. Values applied at execution time, such as Ptero Test Suite values and CSV data for Data-Driven Testing, are configured in Ptero.

Before you start #

• Open the scenario you want to configure in the Scenario Editor panel.
• If the scenario uses repeated values, prepare the Key and Value pairs in advance.
• For a D2D test scenario, decide the device role names first. Example: sender, receiver

Open Scenario Settings #

1. Open the scenario in the Scenario Editor panel.
2. Click the gear icon at the top of the panel.
3. Select the tab you need in Scenario Settings.

General #

Use General to add a scenario description. The description appears as a tooltip when you hover over the scenario name.

When to use it #

Add a Description when teammates need to understand the scenario purpose, test target, or run condition quickly. This is especially useful when a folder contains several scenarios with similar names.

Steps #

1. Open General in Scenario Settings.
2. Enter the scenario description in Description.
3. Click Save.

Check the result #

Hover over the scenario name. The Description you entered should appear as a tooltip.

User Variables #

Use User Variables when a value should be saved as a scenario default.
They are useful for values reused while writing or debugging a scenario, such as an email address, phone number, name, or account value.

For system-provided values such as @OS, use System Variables instead of creating User Variables manually. For the full list, see System Variables.

Values set as User Variables in Stego can be overridden in Ptero Test Suite settings.
If you upload a CSV file, the same scenario can run sequentially with multiple values for Data-Driven Testing.

For execution-time values, see Managing Test Suites.

Before you start #

Prepare the Key and Value you want to reuse in the scenario.

Item	Description
Key	Variable name. Keys cannot contain spaces, cannot be duplicated, and are case-sensitive.
Value	Data assigned to the Key. The Value can be empty.

Steps #

1. Open the User Variables tab in Scenario Settings.
2. Click + Add.
3. Enter Key and Value.
4. Click Save.

Check the result #

The new variable appears in the User Variables tab. Use ${Key} in a scenario step to substitute the saved Value during execution.

Example: If Key is age and Value is 34, ${age} resolves to 34 at runtime.

Edit or delete a variable #

Action	What to do	Check the result
Edit	Change the Key or Value, then click Save.	The updated value appears in the User Variables tab.
Delete	Click the delete button, then click Save.	The variable is removed from the User Variables tab.

Encrypt a value #

Use the lock icon for sensitive values such as passwords. Encrypted values display as ****.

When editing an encrypted value, the existing value is deleted and a new value must be entered.

Runtime #

Use Runtime to configure screen-transition waiting and retry behavior during scenario execution.

Wait for Navigation #

Wait for Navigation is the maximum time Stego waits for a screen transition to finish. Use it to reduce failures caused by the next step running too early during a transition.

Item	Description
Default	3,000 ms (3 seconds)
Disable	Set the value to 0.

Steps #

1. Open Runtime in Scenario Settings.
2. Enter the Wait for Navigation value.
3. Click Save.

Check the result #

The saved value appears in Runtime settings. When you run the scenario, the value is applied as the screen-transition wait between steps.

Self-Healing #

Self-Healing automatically returns to the previous step and retries when a step fails during Motion actions because of a screen transition delay or UIObject recognition error.

When to use it #

Use Self-Healing when the same step fails intermittently because of screen-transition timing or UIObject recognition conditions.

Check the result #

After enabling Self-Healing, run the scenario. If the matching failure condition occurs, the failed step is retried automatically. Review the run result in the Output panel.

D2D Test #

Use D2D Test to configure device roles for Device-to-Device testing. Roles let you run specific steps on devices assigned to those roles.

For example, set the device that sends a message as sender and the device that receives the message as receiver.

Before you start #

• Decide the role names for the D2D test.
• A scenario can include up to 4 roles.

Set up roles #

1. Open D2D Test in Scenario Settings.
2. Turn on the Role Settings toggle.
3. Enter Role Name. Example: sender, receiver
4. Select a device for each role.
   • If no devices are connected, select Random / Android or Random / iOS.
   • If devices are connected, select a connected device directly.
5. Add the required roles, then click Save.

Check the result #

The saved Role Name and device selection appear in D2D Test settings. When you add the scenario to a D2D Test Suite, the Device Roles configured in Stego appear in Ptero Device Settings.

For Ptero D2D Test Suite setup, see Managing Test Suites.

Check before running the scenario #

After saving Scenario Settings, review the following items.

Item	What to check
General	Description is entered for scenarios that need context.
User Variables	Required Keys and Values are saved, and scenario steps reference them in ${Key} format.
Runtime	Wait for Navigation and Self-Healing settings match the scenario run conditions.
D2D Test	For D2D scenarios, Role Settings is enabled and role names are saved as intended.

To run the scenario after checking the settings, see Running Scenarios and Checking Results.