📚Prerequisites:
🛠️Preconditions
Project should have been created.
User should have been assigned to the project.
User should have the QAS client installed.
🔑Privileges
User should have the below privileges:
Import Feature: Import test cases or other project elements.
Manage Scenarios: Control the scenarios within your test suites.
👁️ View Test Scenarios
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.
You can search for the existing scenarios using Search bar.
You can find scenarios by clicking Find.
This will open a popup window in which you can enter text to find. <include screenshot>
If you have a long list of scenarios and you wanted to scroll to the last scenario you were working on, click Scroll to Selection icon.
➕ Create Test Scenarios
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.
When no Test Scenarios are created for the project, you will be asked to Create Scenario from the Explorer section.
If a Test Scenario already exists, click on the + button on the top to add a new Test Scenario.
Click the + button
A new window will appear where you will be prompted to update:
A name for the scenario in Enter Name field.
A short description in Description field. A maximum of 300 characters.
If you intend to create multiple scenarios click on the Create another scenario checkbox.
Once you enter the details, click Create.
If you no longer prefer to create test scenarios, click Discard.
🧑💼Manage Test Scenarios.
🔄Update
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.
Hover mouse over a test scenario to view the Edit option.
Click on the Pencil icon.
Clicking Pencil button, you will be prompted to update:
Scenario Name
Description
Click Save to update the scenario.
❌Delete
Login to Qualitia Automation Studio Client <insert Screenshot>
Access Develop from the left navigation of your Qualitia Automation Studio -Client to view Test Explorer screen.
On the Explorer section, you can view existing Test Scenarios.
Hover mouse over a test scenario to view the Delete option.
Click on the Bin icon.
Note: If the scenario has test cases, you will not be able to delete the scenario. You should delete the existing test cases to delete a scenario. <include screenshot>
💡 Golden Nuggets : Best Practices for Test Scenario Management When managing test scenarios
in Qualitia Automation Studio, a strategic approach can improve efficiency and prevent issues down the line. Here are some best practices to consider:
Test Scenario Distribution: Organize and distribute test scenarios based on project needs but always retain a level of flexibility for unexpected requirements.
Example: In a banking application testing project, organize test scenarios into categories such as Account Management, Transaction Processing, and Reporting. Distribute the scenarios based on the team's expertise and assign testers accordingly. This ensures efficient utilization of resources and expertise.Track Usage: Monitor the application and effectiveness of your test scenarios, ensuring that they are relevant and not overlooked.
Example: Maintain a tracking mechanism or dashboard to monitor the execution and effectiveness of test scenarios. Track the number of times each scenario is executed, the pass/fail rate, and any issues identified. This helps in identifying underutilized or problematic scenarios that require attention.Maintain Validity: Keep your test scenarios updated and relevant to prevent them from becoming obsolete and disrupting operations.
Example: Regularly review and update test scenarios to ensure they remain valid and aligned with the latest software changes. If a new feature is added or an existing feature is modified, update the relevant test scenarios to reflect the changes. This prevents scenarios from becoming outdated and avoids confusion during testing.Modular vs. Comprehensive: Choose between creating separate, modular test scenarios for each functionality or comprehensive test scenarios that cover multiple functionalities based on your testing needs and complexity of the project.
Example: For a complex e-commerce application, consider a modular approach by creating separate test scenarios for functionalities like login, product search, checkout, and payment. This allows for focused testing and easier maintenance. On the other hand, for a simple brochure website, comprehensive test scenarios covering the entire user journey may suffice.Test Scenario Updates: Always remember to update test scenarios when changes are made to the software or when reassigning to another project, maximizing scenario utility.
Example: Suppose a software upgrade introduces a new authentication mechanism in a healthcare application. Update the relevant test scenarios to include the new authentication steps and ensure proper coverage. If the project gets reassigned to another team, review and update the test scenarios to align with their specific requirements and configurations.Regular Reviews: Conduct regular reviews of test scenario allocation and usage to optimize test scenario management.
🔧 Got a problem? Let’s fix!
📞📚 Here to Help: Support and Resources
Need a helping hand? Don't hesitate to reach out to your Qualitia Relationship Manager. For more resources, our official Qualitia documentation and community website are just a click away!