📚Prerequisites:
User should have the QAS - Client installed.
User should be assigned to an existing project.
A test scenario should exist.
🔑Privileges
User should have the below privileges to:
Import Feature: Import test cases or other project elements.
Manage Custom Action Code: Oversee the custom action scripts in projects.
Manage Objects: Control the objects within the testing environment.
Manage Scenarios: Control the scenarios within test suites.
Synchronize Objects: Keep test objects synchronized.
Test Development: Create and update test cases.
👁️View Test Cases
Login to QAS - Client.
Access Develop from left navigation to view Test Explorer screen.
On the Explorer section, you can view existing Test Scenarios.
Click the Expand option on a test scenario, where you can view all its test cases.
Use the Search bar to search for existing test cases.
Use Filter icon to narrow down the search results.
This will open a popup window in which you can enter text to find.
Use the Find option test cases.
This will open a popup window in which you can enter text to find.
The matching results will appear highlighted in orange.
Use Scroll to Selection icon, if you have a long list of test cases and you want to scroll to the last scenario you were working on.
➕ Add Test Cases.
Login to QAS - Client.
Access Develop from left navigation to view Test Explorer screen.
On the Explorer section, you can view existing Test Scenarios.
When no Test Cases exist for a scenario, you are prompted to Add a New Test Case in the Test Case viewer section.
Hover over a test scenario and click + Add a New Test Case to start adding a new Test Case.
You can also click + Add a New Test Case from the middle section.
You can also Add a New Test Case by using the keyboard shortcut:
Windows:
Mac:
Linux:
Clicking Add a New Test Case will open a Create Test Case window with the following fields:
Name: Enter an intuitive name for the test case that is easy to recognize.
Maximum length permitted is 300 characters including spaces.
Scenario: This is a read-only field and defaulted to the Test Scenario under which your Test Case is getting added.
Description: A brief description about the test case.
Manual Test Case ID: Based on the naming conventions your organization follows, enter a unique manual test case ID.
Note: If an ID already exists, you cannot use the same ID.
If you intend to create multiple test cases, click the Create another Test case checkbox.
Once completed, click Create to proceed; otherwise, click Discard.
Clicking Create adds a new test case to the given test scenario.
Repeat steps from 4 through 6 for each additional test case you want to add.
🧑💼Manage Test Cases
You can update and delete test cases for a given scenario.
🔄Update
Login to QAS - Client.
Access Develop from left navigation to view Test Explorer screen.
On the Explorer section, you can view existing Test Scenarios.
Click the Expand option on a test scenario, where you can view all its test cases.
By hovering mouse over a test case, you can view an Edit option.
Click the Pencil icon.
Alternatively, you can select a test case from the middle section and click Pencil icon to edit.
Clicking the Pencil icon, a new window appears where you are prompted to update:
Name: Update a name of the test case.
Maximum length permitted is 300 characters including spaces.
Scenario: This is defaulted to the Test Scenario under which the Test Case is being updated.
Description: A brief description of the test case.
Manual Test Case ID. Based on the naming conventions your organization follows, provide a unique manual test case ID.
Note: If an ID already exists, you cannot use the same ID.
Click Save to update the test case; otherwise, click Discard.
❌Delete
LLogin to QAS - Client.
Access Develop from left navigation to view Test Explorer screen.
On the Explorer section, you can view existing Test Scenarios.
Click the Expand option on a test scenario, where you can view all its test cases.
By hovering mouse over a test case, you can view an Delete option.
Click the Bin icon to delete.
Alternatively, you can select a test case from the middle section and click Bin icon to delete.
<To be written>
💡 Golden Nuggets: Best Practices for Test Scenario Management
When managing test cases in QAS, a strategic approach can improve efficiency and prevent issues down the line. Here are some best practices to consider:
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.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.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.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.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.
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.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.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.
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.
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.
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!