Test Case

Overview

Qualitia is a powerful software testing platform that provides a comprehensive suite of tools to streamline and optimize your testing process. With Qualitia, you can create, manage, and execute test scenarios and test cases with ease and efficiency.

Working with Test Cases

Qualitia provides robust tools for creating and managing test cases. You can create a new test case by providing a unique name and description. The platform supports the addition of preconditions, steps, and expected results for each test case. You can also link your test cases to scenarios and requirements, ensuring traceability and coverage.

The platform provides a user-friendly interface for managing your test cases. You can view all your test cases in a list view, which includes details such as the test case name, description, and linked scenarios and requirements. You can also filter and sort this list based on various parameters.

Qualitia also supports bulk operations, allowing you to perform actions such as delete, copy, move, and export on multiple test cases at once.

In conclusion, Qualitia is a comprehensive testing platform that simplifies the creation and management of test scenarios and test cases, ensuring efficient and effective testing.

Core features

New Test Cases: Create a new test case against a scenario in the Qualitia Automation Studio.

Existing Test Cases: Modify or manage existing test cases that were previously created in the Qualitia Automation Studio.

Delete Test Case: Delete an existing case.

📚Prerequisites:

1. User should have the QAS client installed.

2. Project should have been created.

3. User should have been assigned to the project.

4. A test scenario should exist.

🔑Privileges

User should have the below privileges:

• Import Feature: Import test cases or other project elements.

• Manage Custom Action Code: Oversee the custom action scripts in your projects.

• Manage Objects: Control the objects within your testing environment.

• Manage Scenarios: Control the scenarios within your test suites.

• Synchronize Objects: Keep your test objects synchronized.

• Test Development: Create and update test cases.[SS3] [SS4] 

👁️View Test Cases.

1. Login to

Qualitia Automation Studio Client <insert Screenshot>

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

1. Click E

xpand option on the test scenario.

1. All test cases under the scenario will be listed.

2. You can search for the existing test cases using the

Search bar.

1. You can filter test cases by clicking

Filter icon. [SS5] 

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

2. You can find test cases by clicking

Find.

10.   This will open a popup window in which you can enter text to find. <include screenshot>

11.   If you have a long list of test cases and you wanted to scroll to the last scenario you were working on, click on the Scroll to Selection icon.

‍➕ Create Test Cases.

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

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. <Include Screenshot>

1. When no T

est Cases exist for this scenario, you will be asked to Add a New Test Case in the Test Case viewer section.

1. If a

Test Scenario already exists, hover over the test scenario and click the + Add a New Test Case button to create a new Test Case. Alternatively, you can also click + Add a New Test Case button in the middle section <details section?>.

1. Alternatively, you can also Add a New Test Case by using the keyboard shortcut:

a.       Windows:

b.       Mac:

c.       Linux:  

1. Clicking

Add a New Test Case will open a Create Test Case window with the following fields: 

a.       Name: Enter a name for the test case that’s easy to recognize. Maximum length permitted is 300 characters including spaces.

b.       Scenario:  This cannot be edited and defaulted to the Test Scenario under which this Test Case is getting added. 

c.       Description: A brief description about the test case.

d.       Manual Test Case ID. Based on the naming conventions your organization follows, provide a manual test case ID. Note: If an ID already exists, you cannot use the same ID.

e.       If you intend to create multiple test cases, click the Create another Test case [SS7] [SS8] checkbox.

1. Once completed, click

Create to proceed. Otherwise, click Discard. 

1. A test case will be created under the test scenario selected.

10.   Repeat steps 5,6, 7, 8, and 9 for each additional test case you wish to add.

11.   If you no longer prefer to create test scenarios, click Discard.

‍🧑‍💼Manage Test Cases.

🔄Update

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

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. <Include Screenshot>

1. Click expand option on the test scenario.

2. All the test cases under the scenario will be listed.

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

4. Click Pencil icon.

1. Alternatively, you can select a test case in the middle section <details section?> and click Pencil icon to edit.

1. Clicking on the Pencil button.

2. A new window will appear where you will be prompted to update:

a.       Name: Update a name for the test case that’s easy to recognize. Maximum length permitted is 300 characters including spaces.

b.       Scenario:  This cannot be edited and defaulted to the Test Scenario under which this Test Case is getting added. 

c.       Description: A brief description of the test case.

d.       Manual Test Case ID. Based on the naming conventions your organization follows, provide a manual test case ID.

Note: If an ID already exists, you cannot use the same ID.

11.   Click Save to update the test case.

12.   Click Discard if have accidentally clicked.

❌Delete

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

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.

13.   Hover mouse over a test case to view the Delete option.

1. Click on the

Bin icon.

1. Alternatively, you can select a test case in the middle section <details section?> and click

Bin icon to delete.

1. <To be written> Because QAS client was not working.\

💡 Golden Nuggets : Best Practices for Test Scenario Management

When managing test cases in Qualitia Automation Studio, a strategic approach can improve efficiency and prevent issues down the line. Here are some best practices to consider:

1. Break scenarios into test cases: Once you have defined scenarios, break them down into individual test cases that cover specific functionality or test conditions. Each test case should focus on testing a single aspect or behavior.
   Example: In an e-commerce application scenario called "Checkout Process," break it down into separate test cases such as "Add Item to Cart," "Apply Coupon Code," "Select Shipping Method," and "Place Order." Each test case focuses on testing a specific functionality within the overall checkout process.

2. Create modular and reusable test cases: Design test cases in a modular and reusable manner. This means that test cases can be executed independently and reused in different scenarios or for cross-functional tests. Avoid duplicating test steps or data across multiple test case.
   Example: Create a reusable test case called "User Login." This test case covers the login functionality and can be reused across different scenarios that require user authentication. Avoid duplicating login steps in other test cases and instead reference the "User Login" test case.

3. Define scenario-specific setup and teardown: If certain test cases within a scenario require specific setup steps or teardown activities, define them at the scenario level. This helps in maintaining consistency and ensures that necessary preconditions are set up before executing the test cases.
   Example: In a scenario related to file upload functionality, define the setup steps at the scenario level to ensure that the necessary preconditions are met. This could include actions such as creating test files in a specific directory or configuring the file upload settings before executing the related test cases.

4. Use descriptive scenario and test case names: Provide clear and descriptive names for scenarios and test cases. Use naming conventions that indicate the purpose, functionality, or specific test condition being addressed. This makes it easier to locate and understand the tests.
   Example: Use clear and descriptive names such as "Product Search by Keyword" for a scenario and "Verify Search Results Displayed" for a test case. This naming convention makes it easier to understand the purpose and functionality being addressed without delving into the specific test steps.

5. Use placeholders for test steps: Instead of providing specific test steps, use descriptive keywords or phrases that outline the intended actions. For example, use terms like "perform action A" or "verify result B" without going into implementation details.

6. Focus on test objectives: Clearly state the objective or goal of the test case without specifying the exact steps to achieve it. For instance, mention the expected outcome or behavior you want to validate, rather than the specific actions to take.
   Example: State the objective as "Verify successful payment processing" instead of providing detailed steps on how to achieve it. This focuses on the expected outcome or behavior to be validated rather than prescribing the exact actions to take.

7. Document test assumptions: If there are any assumptions related to the test case, explicitly state them in a separate section. Assumptions can include prerequisites, specific system states, or test environment conditions. By doing so, you keep the test steps independent of these contextual factors.
   Example: In a test case, explicitly state assumptions such as "Assumes a valid user account already exists" or "Requires a stable internet connection." This clarifies the preconditions or contextual factors without embedding them within the test steps.

8. Exclude specific test data: Avoid including specific test data or examples within the test cases. Instead, indicate the type or characteristics of the data required without providing actual values. This allows for flexibility in selecting appropriate test data during execution.

9. Refer to external sources: If there are external resources, documents, or specifications to be used during the test, mention them without embedding the actual content. This approach maintains the test case's independence from specific reference materials.

10. Separate test configuration details: Keep any configuration or setup details separate from the test case itself. If there are specific configurations required for the test, refer to them without providing the actual configuration values or steps.

11. Regular Reviews: Conduct regular reviews of test cases 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!