...
🚀 In summary, Qualitia Design Studio is a powerful, efficient, and user-friendly platform that can significantly enhance your test automation lifecycle. Its intuitive features, ease of use, and robust capabilities make it an invaluable component of your toolset. Experience the power of QDS today and elevate your custom solutions and products to new heights.
🔑 Prerequisites:
🚀 Let's Get Started with QDS
Imagine you are an automation tester preparing to kick off application testing. The Qualitia Design Studio (QDS) is your go-to for this task. This platform helps to create a scalable, maintainable test automation design. It offers clear traceability from your requirements right through to your automation test cases.
The idea is simple. First, you create manual test cases in the QDS to verify requirements. Then, you synchronize these manual test cases with the Qualitia Automation Studio (QAS), where you develop your automation scripts.
But Before You Dive In...
Keep in mind the following when working with QDS integrated projects:
Only one QAS project can synchronize with one QDS project, and vice-versa.
You can only set up integration with a QDS during the creation of the QDS project.
Make sure your role has the Test Development privilege.
You will find a Requirements screen in the Development section instead of the Test Case Editor screen. This screen is equipped with the features of the Test Case Editor, plus additional capabilities for synchronizing and sharing with the QDS project.
You cannot import tasks from a different project using the Import Task feature.
You cannot create test cases in QAS. You have to create them in QDS first and then Share for Automation. After that, you can edit or delete these test cases.
When creating a new project, all existing objects will be synchronized along with tasks and test cases shared for automation in the QDS. After this, you can only edit or delete objects in the QAS.
Test cases and tasks will only be accessible in the QAS after they have been shared for automation from the QDS.
If you are using Bitbucket (GIT) for version control, first create a project branch in the Bitbucket repository and then set up the project in QAS.
The Nitty-Gritty of QAS Project Synchronization with QDS
Here is how you set up synchronization between a QAS project and a QDS project:
· From the Expand Menu, choose Project. You will see a list of available projects.
·
Login to Qualitia Automation Studio Client <insert Screenshot>
Access Projects from left navigation of your Qualitia Automation Studio -Client to view Project Explorer screen.
On the Explorer section, you can view existing Projects. <Include Screenshot>
Click New and enter
...
Project Name
...
Description.
...
Enable the Design Studio Integration option. This lets you synchronize this project with the QDS.
| Note |
|---|
Bear in mind that once you have done this, you cannot undo it. |
...
Click Next and then select Continue with Integration.
...
Click Add to add a new row to the list of users.
...
Double-click the User ID field to select the user.
Double-click the User Role field to assign a role to this user.
...
Click Next.
...
Now, you need to fill in your QDS details: enter the
QDS URL
...
QDS Username and Password
...
Select a QDS Project to synchronize your project with.
You will see an overview of all relevant project artifacts of the QDS project.
...
Click Done. Your new project, complete with all project artifacts from the QDS project, is now created.
Importing Test Artifacts from Design Studio
The first-time synchronization of test artifacts happens automatically when you create the QAS project. After this, any modifications to test cases and tasks will only be done in the QAS.
...
When new test cases are updated in QDS, you can bring them into the QAS through synchronization:
· From the Expand Menu, go to Develop.
· Go to the Develop or Execute section.
...
Login to Qualitia Automation Studio Client <insert Screenshot>
Access Develop or Execute from left navigation of your Qualitia Automation Studio -Client to view Test Explorer screen.
From the top right corner of the Requirements screen, hit the Sync button.
A Change Log Review window
...
will pop up, summarizing all changes being synchronized from QDS.
...
Review the report.
...
Choose either:
...
OK to merge all changes with existing requirements.
...
Cancel to continue working without merging changes.
After you have done this, all newly added manual objects, tasks, and test cases from QDS will be imported into the QAS.
Updating Manual Test Cases
In order to access manual test cases in the QAS, you need to share them for automation from QDS. Once they have been shared and synchronized, you can then update these test cases:· From the Expand Menu, choose Develop. Here, you
Login to Qualitia Automation Studio Client <insert Screenshot>
Access Develop from left navigation of your Qualitia Automation Studio -Client to view Test Explorer screen.
On the Explorer section, you can view existing Test Scenarios and Test Cases. <Include Screenshot>
You will find all manual test cases that have been synchronized from the QDS.
...
From the top right corner of the Requirements screen, hit the Sync button
...
.
...
To start working on any test case, right-click the manual test case and select Implement. Now you can edit this test case.
...
Once a test case has been synchronized with the QDS, you need to implement it before you can edit it or include it in a suite execution.
...
Add steps and tasks by either recording the steps using the Qualitia Automation Recorder, or by editing the test case manually.
...
Once you have added all necessary steps and actions,
...
click Save.
...
Click the Share button to synchronize the updated test case with the QDS project.
| Note |
|---|
After sharing with QDS, the QAS will lock the test case. You can only unlock it from the QDS. |
Sharing Tasks and Test Cases for Design Updates
Sometimes, manual test cases need design-level updates. In these cases, you can share automated test cases and tasks with the QDS for updates:
· From the Expand Menu, choose Develop.
·
Login to Qualitia Automation Studio Client <insert Screenshot>
Access Develop from left navigation of your Qualitia Automation Studio -Client to view Test Explorer screen.
On the Explorer section, you can view existing Test Scenarios and Test Cases. <Include Screenshot>
Click Tasks.
In the Tasks section, choose the tasks you want to share for design updates.
| Note |
|---|
After you have done this, the tasks and test cases cannot be edited or removed from the QAS. They will also show a lock icon before their names, indicating they have been shared for design updates. |
Sync History
Finally, do not forget to review your sync history. You will find the date and time of each operation, as well as details of the tasks, test cases, and objects that were synchronized.
...
That's it, you are all set. Now go forth and automate!
...
💡 Golden Nuggets: Best Practices for Workspace Management
Managing your workspace effectively is vital in the realm of software testing. Here are some best practices to consider:
Unique: Workspace names should be unique to each workspace to eliminate any chance of confusion and potential mismanagement.
Avoid Sensitive Information: It is a good idea to steer clear of including sensitive data like client identifiers, confidential software details, or strategic plans in your workspace names. Such information can be misused if it falls into the wrong hands.
Easy to Remember: While workspace names should be memorable, ensure they do not reveal any sensitive information.
Appropriate Length: Striking a balance with length is key. Names that are too short may lack context, while overly long ones may be challenging to recall. A recommended range is between 6 to 14 characters.
No Special Characters and Spaces: To avoid compatibility issues, it is recommended not to include special characters or spaces in workspace names. However, underscores are acceptable.
Consistent Format: If you are handling numerous workspaces, employing a consistent naming format can facilitate easier management. This could be based on software type or team name (e.g., Ecommerce_Workspace_Regression or Microsoft_Workspace_UITesting).
Steer Clear of Offensive Words: Maintain professionalism by ensuring workspace names do not include any offensive or inappropriate language.
Review: Regularly review your workspace statuses to maintain momentum and avoid bottlenecks. Keeping your workspace data current promotes effective communication and collaboration.Archive vs Delete: If your workspace is temporarily inactive, consider archiving it rather than deleting. However, if the workspace is permanently closed or completed, deleting it may be the better option.
🔧 Got Trouble? Let's Fix!
If you are finding it challenging to create a workspace, we have your back! Here are some troubleshooting tips:
...
If after trying these steps you still cannot create a workspace, reach out to your Qualitia Relationship Manager. They are on standby to help you navigate any roadblocks on your journey with Qualitia Design Studio.
📞📚 Here to Help: Support and Resources
Need some assistance? Don't hesitate to contact your Qualitia Relationship Manager. For additional resources, our official Qualitia documentation and community website are just a few clicks away! Experience an effortless journey with Qualitia Design Studio.
...