Opening a Workspace #
Before authoring a scenario, complete the following three tasks:
- Specify a Workspace Folder
Select a folder to store scenarios. - Create Folders
Organize scenarios by creating folders within the Workspace folder. - Create Scenario Files
Generate scenario files inside the created folders.
What is a Workspace? #
A Workspace is a folder where scenarios authored in Stego are stored.
When Stego is first installed, a default Workspace is automatically set, but users can manually change its location.
A Workspace can contain multiple folders, each holding numerous scenarios for better organization.
Specify a Workspace Folder #
The following steps explain how to specify a Workspace in Stego:
1. Opening the Default Workspace
From the menu bar, select Workspace > Open Default to access Stego’s default Workspace.
2. Opening a New Workspace
Step 1. From the menu bar, select Workspace > Open.
Step 2. Select a folder to use as the Workspace.
Step 3. The name of the selected folder is displayed at the top of the screen.
Add Folder #
What is a Folder? #
A folder is used to manage scenarios within a Workspace.
- Note
It is recommended to create and manage separate projects for each target application.
This approach allows for better organization of scenarios systematically across different applications.
Creating a Folder #
Step 1. To create a new folder within the Workspace, click the + button.
Step 2. Enter the name for the new folder.
Selecting a Folder #
To view the list of scenarios in a specific folder, follow these steps:
- Select from the Folder List
Click the desired folder in the folder list. - Check the Scenario Panel
The scenarios within the selected folder will be displayed in the scenario panel below.
(Example of clicking the ‘Examples’ folder to display the list of scenarios contained within it in the Scenario Panel)
Adding a Scenario #
Scenario management is divided into two categories: Scenarios and Common Scenarios
What is a Scenario? #
A scenario is an automated script created based on test cases.
It consists of multiple steps that perform various actions, and when executed, the steps are processed sequentially from top to bottom.
What is a Common Scenario? #
A common scenario is designed for reuse in multiple scenarios, such as Scenario A and Scenario B, which share overlapping steps.
This enhances reusability and simplifies maintenance.
For more details on creating and using common scenarios, refer to the Common Scenario.
Creating a Scenario #
① Click the + button in the Scenario Panel.
② Enter a name for the scenario. The new scenario will be created upon entering the name.
Importing a Scenario #
① Click the 
button in the Scenario Panel.
② Select a scenario file with the .stego filename extension.
③ Click Open to import the scenario into Stego.
Exporting a Scenario #
① Click the 
button in the Scenario Authoring Panel.
② Select a folder to save the scenario.
③ Click Save to generate the scenario file in .stego format.
Step-by-Step Scenario Authoring #
The scenario authoring process consists of the following steps:
- Creating Steps
- Analyzing the Device Screen
- Selecting and Adding Screen Elements to Steps
- Testing the Created Steps
- Saving the Scenario
Repeating steps 1 through 3 allows you to create multiple steps, ultimately building a complete scenario.
Details for each step are provided below.
1. Creating Steps
#
There are two ways to create steps.
① Using the + Button
Click the + button (①) located in the top toolbar to create a step.
It is useful when you want to quickly add a new step.
② Using the Insert Menu
Right-click to access the Insert menu (②) to create a step at a specific location.
It is suitable when you want to insert a step at a precise position.
- Insert child : Adds a step under the selected step. Used to add child steps that will be executed based on conditions such as If or Loop statements.
(This option is only activated when child step addition is possible.) - Insert above : Adds a step above the selected step.
- Insert below : Adds a step below the selected step.
Modifying Created Steps
The default action for a created step is Touch. You can change this to other actions as needed.
- Changing Step Action
To change an action, click the ▼ button of the corresponding step and select from the available actions.
For more details on functions and usage methods of each action, refer to the Action List.
This document includes configuration options and use cases for each action to facilitate more effective implementation.
After creating steps, it’s crucial to verify if their order and names are appropriate. This helps maintain clear scenario flow and easy step identification.
③ Changing Step Order
Step order can be modified using drag and drop.
Click the 
icon shown in ③ above and drag it to the desired position to adjust the order.
④ Modifying Step Names
When a step is created, it’s automatically named “Unnamed” (see ④ above).
Please change it to a name that clearly indicates the task the step performs.
If all names remain the same, it can be difficult to distinguish between steps, making scenario understanding and management challenging.
2. Analyzing Device Screen #
To accurately perform the action assigned to a step, you need to analyze the app screen where the action will be executed.
Screen analysis starts when you click the Screen Analysis Icon marked with AI letters in the top right of the device panel.
(Screen Analysis Process)
Various screen analysis tools are available to improve scenario creation efficiency and accuracy. When screen analysis is first executed, the system applies Object Detection (OD) method by default to analyze screen elements and provide results.
For detailed explanations and usage methods of each screen analysis tool, refer to the Screen Analysis Tools.
3. Adding Screen Elements to Steps #
① Select the target element for the action from the screen analysis results.
② Drag & drop the selected screen element to the empty field next to the step’s action.
During scenario execution, the configured actions will be executed sequentially based on the screen elements added to each step.
4. Testing Created Steps #
(The screen that automatically notifies when a different UIObject is matched instead of the expected one.)
When a screen element is added to a step, the system automatically verifies if the element can properly perform the action.
If issues are found during verification, the system displays the UIObject Field window (①) along with an automatic test result message (②).
Refer to the Detailed Screen Element Settings to improve the accuracy of UIObject matching.
5. Saving Scenarios #
After modifying a scenario, you need to save the changes.
When there are modifications to a scenario, a yellow circle icon appears next to the scenario name at the top of the writing panel, indicating that saving is needed.
There are two ways to save a scenario:
- Click the Save icon(
) in the top toolbar. - Use the shortcut key Ctrl+S (⌘+S for Mac users).
Note) Scenarios are not automatically saved in real time, so please save your work frequently while writing.