Configuring Recorded Scenario
The Record Scenario feature helps you record a scenario, edit its steps, add assertions, and modify UI elements. Record a scenario using the Offline Recorder, apply custom tags, edit recorded scenarios, add assertions, and edit UI elements — all from the Test Design screen.
The Record Scenario feature lets you record a scenario, apply custom tags, edit recorded scenarios, add assertions, and edit UI elements. To record a scenario, follow the instructions in Record a Scenario Using Offline Recorder. To use custom tags, follow the instructions in Batch Execution and Configure Custom Tags.
Editing a recorded scenario
Perform the following:
After the nodes are created, navigate to Test Design and scenario names, custom tags, and scenario outlines are listed.
Here you can record a scenario by clicking Record Scenario.
In the Record Scenario pop-up window, enter the scenario name, outline the steps briefly, and click Submit to create a sequence.
If you choose to edit the recorded scenario, then click the Scenario Edit.
For more information, see Managing Test Cases using Edit Scenario Feature.
Adding Assertions
Perform the following:
Repeat the step 1 and step 2 from the preceding section.
All the available nodes are listed in the window.
In this window, select the required node, required feature, and UI elements.
In the Controls pane, click the Show icon dropdown and select the Assertion checkbox.
The assertion will be available in the Controls list.
While adding UI elements, you can select the default action as 'wait in seconds' to the UI element to appear.
For example, after you wait for a UI element like a button to appear, you can use an assertion to verify that the button is visible or clickable.
- Action: Wait for 5 seconds for the button to appear.
- Assertion: After waiting, the test checks if the button is visible on the page.
This combination of wait and assertion ensures your test only proceeds when the element is ready and confirms it is working as intended.
Click Save and Close.
Scenario workflow has been recorded. \
Note: Case-sensitive variations of the same name are restricted to prevent duplicate entries. For example, names such as Home page, Home_page, Homepage, homepage, home page, home_page, HOME PAGE, and HOME_page are treated as duplicates and cannot be created separately.
Editing the UI elements
Perform the following:
Repeat the steps 1 and 2 from the Editing a recorded scenario section.
Click Scenario List and select a scenario.
Click the Edit icon beside a scenario.
Click the Edit icon beside a GWT step.
The Edit Step pop-up window appears for you to add a new name (alias name) for an existing UI element.
In this window, click the Show More link to expand the details of the UI elements.
The following table provides the Edit Control pop-up window details:
| Field | Description |
|---|---|
| Alias Name | If you choose to add a new name or modify an existing name for a UI element or a control, then you can use this text box. |
| Default/Custom Action | Default actions are the ones readily available as part of the automation framework in algoQA. algoQA platform allows you to create custom actions to incorporate your application-specific testing requirements. You can select the default/custom action from the dropdown list. |
| TestStep Settings | You can select a specific condition or a parameter from the dropdown list. Allows you to customize your test steps by selecting or excluding specific conditions, ensuring that only relevant steps are included. For example, if you wish to avoid generating the default post-condition step, you can select the 'No Postcondition' option from the dropdown. This will prevent the default last step from appearing in the Feature File. |
| Step Input | To add a prefix to a GWT step, you can update the textbox. By default, the initial context in a Given step is shown as "I". For example, 'Given I have access to application' sets up the initial state for the test. |
| Custom Value | You can provide user-specific values, keywords, and parameters in the custom value text box. It will be reflected in the Feature File. For more information, see Keywords Used in algoQA and Their Descriptions. When entering a value in the custom value field, adhere to the following: Custom value cannot be just blank spaces. If you wish to include spaces, you can use the keyword _empty_. For more information, see Keywords used in algoQA. If you press the spacebar to enter only spaces, then the following error message is displayed: You can include spaces at the beginning, end, or between words. |
| Message | You can provide a comment or text for a particular GWT step. When entering a value in the message field, adhere to the following: Message field cannot be just blank spaces. If you wish to include spaces, you can use the keyword _empty_. For more information, see Keywords used in algoQA. If you press Enter to enter only spaces, then the following error message is displayed: You can include spaces at the beginning, end, or between words. |