Page Comparison

This document covers the prerequisites to add, update, and delete Test Scenarios in Qualitia Automation Studio (QAS).

📚Prerequisites:

🛠️Preconditions

1. Project User should have been createdQAS - Client installed.

2. User should have been be assigned to the project.User should have the QAS client installedan existing project.

🔑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

...

Suites 

To view an existing test suite:

1. Login to Qualitia Automation Studio QAS - Client. <insert Screenshot>

2. Access Develop from left navigation of your Qualitia Automation Studio -Client to view the Test Explorer screen.

   1. On the Explorer section, you can view existing Test

   Scenarios

   1. Suites.

3. You Using the Search bar, you can search for the existing scenarios using Search barsuite.You

4. Using Find, you can find scenarios by clicking Findthe existing test suites.

   1. This will open a popup window in which you can enter text to find.

   <include screenshot>If

   2. The matching results will be highlighted in orange color.

5. Use the Scroll to Selection icon, f you have a long list of scenarios test suites and you wanted to scroll to the last scenario you were working on, click Scroll to Selection iconone.

‍➕ Create Test Scenarios

...

Scenarios 

To create a new test scenario:

1. Login to Qualitia Automation Studio Client <insert Screenshot>QAS - Client.

2. Access Develop from left navigation of your Qualitia Automation Studio -Client to view Test Explorer screen.

   1. On the Explorer section, you can view existing Test Scenarios.

3. When no Test Scenarios are created for the project, you will be asked to Create Scenario are prompted to create a scenario from the Explorer section.

4. If a Test Scenario already exists, click on Click the + button on the top to add a new Test Scenario.Click

5. By clicking the + button, A new window will appear where you will be prompted to update:

   A

   appears where can add:

   1. An intuitive name for the scenario in Enter Name field.

   2. A short brief description in Description field. A maximum

      1. Maximum of 300 characters.

   3. If you intend to create multiple scenarios, click on the Create another scenario checkbox.

6. Once you enter the details, click Create; otherwise, click Discard.

   1. Clicking Create adds a new test scenario.

7. If you no longer prefer to create test scenarios, click DiscardRepeat the steps 4 through 6 for each additional test scenario you want to add.

‍🧑‍💼Manage Test Scenarios

You can update an existing test scenario and delete an unwanted or redundant test scenario.

🔄Update

  To update an existing test scenario:

1. Login to Qualitia Automation Studio Client <insert Screenshot>QAS - Client.

2. Access Develop from left navigation of your Qualitia Automation Studio -Client to view Test Explorer screen.

   1. On the Explorer section, you can view existing Test Scenarios.

3. Hover mouse over a test scenario to view the Edit option.

4. Click on the Pencil icon .Clicking Pencil button, you will be and you are prompted to update:

   1. Scenario Name

   2. Description

5. Click Save to update the scenario.

❌Delete

To delete an unwanted or redundant test scenario:

1. Login to Qualitia Automation Studio Client <insert Screenshot>QAS - Client.

2. Access Develop from the left navigation of your Qualitia Automation Studio -Client to view Test Explorer screen.

3. On the Explorer section, you can view existing Test Scenarios.

4. Hover mouse over a test scenario to view the Delete option.

5. Click on the Bin icon to delete. 

...

...

...

...

💡 Golden

...

Nuggets: Best Practices for Test Scenario Management

When managing test scenarios

...

in Qualitia Automation Studioin QAS, a strategic approach can improve efficiency and prevent issues down the line. Here are some best practices to consider: 

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. Regular Reviews: Conduct regular reviews of test scenario allocation and usage to optimize test scenario management.

...