- StudioPro
- Orchestrator
- Testing robots
- Test Manager
Managing Test Cases
Test Cases can be either manual or automated or both. You can start by creating manual tests and later automate them. Tests that contain both manual steps and automation can be executed manually or automated. From a result perspective, this makes no difference.
To create test cases in a Test Manager project:
Navigation and Search
To quickly find your test case, use the search function and the filters. Navigate within the page using and configuring the paginator. Alternatively, you can use the breadcrumb to navigate between the pages.
-
Search - You have two filter tabs to choose from:
- Browse - to list all test cases.
- Updated by me (predefined) - to list only the test cases that have been updated by the current user, running the Test Manager instance.
- Filter - Use the search bar to find test cases by their key, name or labels (requires full search term match).
To add automation to an existing test case in Test Manager proceed as follows:
Manual Test Cases
Adding Manual Steps to a Test Case
To make a test case a manual test case, you need to add manual steps to it. Manual steps define actions for manual testers that need to be executed in a defined order. These actions might just be simple user interactions on the user interface or contain verification operations that need to be carried out by the tester. Each action consists of a description and an expected behavior. The latter is an optional description of what should happen after the aforementioned action has been performed. For convenience, a Clipboard value can also be defined on a step. This value is copied to the Clipboard whenever that particular step is executed, so the user does not have to manually type into the input fields.
To add manual steps to a test case open it and in the Manual Steps tab, click CLICK TO ADD A NEW TEST STEP.
Each step can be expanded or collapsed to improve readability. Enter a description and optionally an expected behavior. This can just be a statement about what is expected to happen or can be a verification like “VAT is displayed as 32.44“.
{CLIPBOARD}
anywhere in the description. During execution, this expression will be replaced by the Clipboard value to improve readability.
During execution, this step looks like this:
The email address is in the Windows Clipboard so the tester can enter it by pressing Ctrl + V.