Test Steps
Last updated
Last updated
A Test Step is defined as an "action" that can be performed on a Desktop Application. It is considered a single unit of a test script. A test step consists of several properties, with the main property being the 'Action Types,' which specify the nature of the action to be performed on the Desktop Application (e.g., "Click," "Set," "Start," etc.).
Previously Created Project
Previously Created Module
Previously Created script
Test steps comprise four essential components:
Action Type – Describes what the step will do.
Description - Provides a relative description for the step.
Locator Type & Locator Value – Specifies what the step will interact with.
Control Type - The "Control Type" refers to the type or class of a GUI element (such as buttons, checkboxes, text fields, etc.) that you are interacting with. This information is essential for automating interactions with applications.
Depending on the action type used, additional data and parameters may be required.
The first step we are going to create, and one of the most common first steps is a launch:
"Launch" is the action type used to open an application, serving as the essential initial step for executing scripts.
To navigate to the proper action, click the dropdown → "Select Action Types" → "Launch"
Next, enter a relevant description.
Lastly, copy and paste the location of the application (e.g., C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Wordpad.lnk ).
Note:
The above path is a sample path; the user should add the path of the application they want to launch
Click the "Add Step" button to add the next steps and construct test steps.
Users have a range of step management options at their disposal for enhanced control and flexibility:
Parameterize Step: Users can parameterize steps by introducing variables that can be dynamically replaced with values during execution, allowing for more versatile and data-driven testing.
Note: Refer to the TDM documentation for more information.
Enable Screenshot for Step: Users can opt to capture screenshots during the execution of a specific step, providing visual documentation and confirmation of the step's execution results.
Mark Step as Optional: For scenarios where certain steps are conditional or non-critical, users can mark steps as optional, ensuring test execution continues even if the step fails.
Insert Step: Users can insert new steps at any point within a Test Steps, enabling them to refine and expand their testing scenarios with ease.
Expand/Collapse Step: Users can expand or collapse individual steps, simplifying navigation through complex test cases and improving readability.
Users have a range of step management options to ensure an efficient workflow:
Delete Step: Users can remove unnecessary steps with ease, keeping test cases concise and relevant.
Move Step Below: For better organization, users can rearrange steps by moving a selected step below another step.
Move Step Above: Similarly, users can enhance the order of steps by shifting a selected step above another step.
Move Step To: Users can relocate steps to a different position within the Test Steps by specifying the step number, tailoring the sequence to the testing requirements.
Clone Step: By duplicating steps, users can quickly replicate a step's actions and parameters, streamlining Test Step creation.
These versatile options empower users to maintain clarity, streamline processes, and adapt Test Steps to evolving needs.
Users have various options to manage the Test Steps.
Save Test: Users can securely save their test progress, ensuring that their work is preserved for future use or modifications.
Clone Script: With a single click, users can duplicate an existing script, expediting the creation of similar tests while maintaining the original script.
Save and Update Test Scripts: After making edits in the Test Steps, you can effortlessly save and update the test script linked to a Test Suite in the Test Lab/Sprints.
Create Restore Point: Users can create restore points to capture a snapshot of their test script's current state. This allows them to revert to a specific version in case of unexpected changes or errors.
These robust options empower users to manage their test scripts effectively, streamline workflows, and ensure accuracy in testing processes.
Click the "Save" button.
Enter the required details and click on Save .
Click the "Save" button.
Select the "Suite" which you want to update and click on Save .
Note: This will update the particular Test Script of the selected Test Suite in the Test Lab/Sprints.
Click the "Save" button.
Select "Create Restore Point" from the dropdown.
Enter the required details and click on Create Restore Point .
A restore point will be created with the given details.
You can navigate to the Versions tab in the right panel to Restore the Test Steps.
Note: When a user clicks on restore, all the newly created steps that are not part of the restore point will be removed
The side panel provides you with a range of convenient options to streamline the testing workflow:
Auto Save: The auto-save feature ensures that your changes are saved automatically every 5 Minutes, minimizing the risk of data loss.
Edit Steps: Effortlessly fine-tune your test case steps with the edit option. Make necessary adjustments on the fly for precise test case definition.
Expand/Collapse Steps: Navigate through your test cases with ease by expanding or collapsing All steps. Simplify complex test cases for better readability.
Record Steps: Seamlessly capture your interactions with the application using the QloudBridge software. Easily translate the actions performed on the app into Test Steps
Import File: Save time by importing test data or scripts from external files. Integrate data-driven testing effortlessly into your workflow.
Script Linked to Suites: The list of the Suites will be displayed here to which the selected Script is linked.
With these versatile actions available in the side panel, you can take your testing to new heights, optimizing productivity and ensuring the highest quality for your applications.
Global Variables, a feature that lets you create environment-specific variables and seamlessly integrate them into your test steps by appending the variable name with #variable#. Here's how to make the most of this capability:
Navigate to the 'Global Variable' tab in the side panel.
Click on the dropdown to select the "Environment"
Select the desired environment from the dropdown, which you want to access the variables.
Copy the required variable by clicking on the 'Copy to Clipboard' icon.
Paste the copied variable into the field where you intend to use it.
This intuitive process empowers you to efficiently manage your data and configurations, making testing more flexible and dynamic. Experience the convenience of using Global Variables to enhance your testing workflow.
Select "Clone Script" from the dropdown.
Select "Save and Update Test Scripts" from the dropdown.
