System Variables are execution values provided by the system.
They are available in some scenario actions without being created by the user.
Use System Variables when a scenario needs values that depend on the run environment,
such as the current device, operating system, active app, or clipboard value.
Before you start #
- System Variable names start with
@, such as@OS. - Read-only variables cannot be changed manually.
- Editable variables may affect later steps in the scenario. Check how the value is used before changing it.
- For values that you define yourself, use User Variables in Configuring Scenario Settings.
System Variables #
| System Variable | Description | Editable |
|---|---|---|
@OS | Operating system of the device. Example: Android, iOS | No |
@OS_VERSION | Operating system version. Example: 14.4, 13.0.1 | No |
@MODEL_NAME | Device model number. Example: SM-G991N | No |
@DEVICE_NAME | Device name. | No |
@ACTIVE_APP_ID | Package Name or Bundle ID of the app currently shown on the screen. | No |
@HTTP_PROXY_SERVER_URL | Proxy server URL used for HAR (HTTP Archive format) collection. | No |
@HTTP_PROXY_PORT | Proxy server port used for HAR collection. | No |
@AUTHORING_MODE | Shows ON when the scenario runs in Stego and OFF when it runs in Ptero. | No |
@CLIPBOARD | Value currently stored in the device clipboard. | Yes |
@WAIT_FOR_NAVIGATION_TIMEOUT | Screen-transition wait time between steps, in ms. The default value is 3,000. | Yes |
@PHASE | The last stored value is automatically added as a label in Ptero test results. | Yes |
Related documents #
- To define values in a scenario, see Configuring Scenario Settings.
- To override values at execution time or test multiple values from a CSV file in Ptero, see Managing Test Suites.