Test Design Folders
qTest Manager allows you to create reusable test cases and stored them in a central repository in the Test Design module. Then, using the drag/drop functionality within the left navigation panel and you can move test cases and folders into the preferred layout. For more information, see the article Examples to Build Your qTest Repository.
Create Test Cases
Before we can execute test cases, we need to create them in the Test Design module. Then, we create test runs from the Test Execution module to plan and log execution results.
- To create a test case, select the Test Design module.
- Click the New Module icon in the left panel. This is the first icon from the left.
HINT: Test cases, like Requirements, are organized in folders known as project modules. Before creating a new test case in qTest Manager, make sure to create at least one project module to organize your test cases. We recommend organizing test cases into a nested folder structure to make them easy to find.
- Click the New Test Case icon in the left panel and enter a title for the test case at the top of the page. This is the second icon from the left.
HINT: The Status, Type, Version, and Priority fields are automatically populated by qTest Manager. You can change the status, type and priority of the test case, as applicable. To create custom fields or modify existing system fields, see the Field Settings article.
- Click the down arrow to the right of the Assigned To field and click the checkbox next to the name of the tester you want to assign to this test case.
HINT: You can automatically send email notifications to other users when test cases (or other objects) are assigned to them. To configure email notifications, see the Notification Settings article.
- In the Description text box, enter a description of the test case.
- In the Pre-condition text box, enter the pre-conditions that must occur prior to executing this test case.
- In the Test Steps area of the screen, enter the steps to execute this test case. For each step in the test case, enter a description of the step in the Step Description field followed by an expected result of performing that step in the Expected Result field. For example, if the step description is to “click the Resources button”, the expected result is “the Resources page is displayed.”
- Click the Save button to save the test case.
Edit Test Case
To edit a Test Case, you need Edit Test Cases permission. To edit an existing Test Case, perform the following steps.
- Select an existing Test Case in the Test Design tree.
- Edit the Test Case name or any fields in Properties, Test Steps, Resources, and Attachments of the Test Case.
- Click the Save button to finish editing Test Case. (You must always save after you finish editing so your changes are not lost.)
- Click Reload to get the latest information on the selected Test Case.
Test Case Versioning
When a test case is saved with new changes, the Test Case's version will automatically increase by 0.1. The version number is visible as a system field on the test case page, as shown below.
When editing the test case, you can only make changes based on the latest version of the test case, not previous versions. To easily reference the changes made over time, see the History tab of the test case, as displayed below.
When executing test runs in Test Execution, you can select any previously-approved version of the test case. If you have the permission to Approve a Test Case, you will also be able to execute the latest version of the test case during runtime.
Test Case Versioning and Software Versioning
A new version of software may require changes to the tests that must be performed. To manage changes to a certain test over time, you can either edit the original test case (e.g., add additional test steps) or copy the original or create a brand new test case. This separate test case may be more beneficial if you need to continue to test previous versions of your software.
If it is not as important to continue testing older versions of your software, you can edit the existing test case over time.
Approve a Test Case
To help enterprise testing teams coordinate test design activities, qTest Manager provides the ability to control how changes to a test case can be incorporated into Test Execution. An Approved Test Case means that this version is ready for test execution.
If only certain users within your project should have the ability to review and “approve” test case changes, the Project Administrator can remove the “Approve Test Cases” permission from other users in your project’s User Management Settings. If it is not important to restrict who can approve test cases within your project, simply give every user the permission to “Approve Test Cases”.
To identify whether a test case is in an approved version, refer to the test case version number. When a test case is approved, the Test Case's version will automatically increase to the next whole number. For example, when test case version 4.2 is approved, the version number is automatically changed to test case version 5.0. The approved version of edited Test Cases will be automatically updated in their Calling Test Cases.
To approve a single Test Case, click the Approve button at the top-right of the Test Case page. Click on Yes in the confirmation pop-up.
To approve multiple Test Cases, go to the Data Query in Test Design, query for Test Cases that need to be approved. Then, select the Test Cases in the Query Result table and click the Batch Approve button to approve all selected Test Cases.
Delete a Test Case
- Deleting Test Cases will remove their associations with any Requirements.
- If you delete a Called Test Case, it will remove all corresponding steps within Calling Test Cases that included the Called Test Case.
- Deleting a Test Case will automatically remove its associated Test Run(s) in Test Execution regardless of their execution status.
HINT: Requirements linked to deleted Test Cases will remain unchanged. Deleted Test Cases can be restored from the Recycle Bin.
NEXT STEPS: See the following articles.