- Getting started
- Project management
- Documents
- Working with Change Impact Analysis
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- Linking test cases in Studio to Test Manager
- Delete test cases
- Manual test cases
- Importing manual test cases
- Document test cases with Task Capture
- Parameters
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governeed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Applying filters and views
- Importing Orchestrator test sets
- Creating test sets
- Adding test cases to a test set
- Assigning default users in test set execution
- Enabling activity coverage
- Enabling Healing Agent
- Configuring test sets for specific execution folders and robots
- Overriding parameters
- Cloning test sets
- Exporting test sets
- Applying filters and views
- Accessibility testing for Test Cloud
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Test Manager user guide
Add manual steps to define actions that need to be executed sequentially, such as simple user interactions or containing verification operations performed by the testers.
Adding Manual Steps to a Test Case
You can add a maximum number of 250 test steps to a manual test case. To add manual steps to a test case, follow these steps:
- Open your project in Test Manager. If you do not have a project yet, see Creating a Project.
- In the left navigation panel, go to Test Cases.
- Click the test case key to open it.
- Go to Manual Steps and click a step to expand the panel.
- Configure the following step details:
- Precondition (optional): List the tasks you must execute before the testing starts. This isn't part of the test case workflow, but you have to do these tasks before you start the actual steps.
- Description: Add a short and concise description.
- Expected Behaviour: You can state whether something is expected to happen or to be verified (e.g.
VAT is displayed as 32.44). - Clipboard data: You can define a Clipboard value so you do not have to manually type into the input fields. For a specific use case scenario, see Copying Clipboard Values
(For Cloud Commercial and Cloud Public Sector only) The character limit for the Clipboard data field is 8000 characters.
. :::note * Consider adding a single action for each step. * To duplicate, delete and reposition the steps, click the vertical ellipsis on a step and choose an action from the dropdown list. :::
Figure 1. Adding steps to a manual test case with precondition and postcondition
- Postcondition (optional): Specify the expected state of the application after the test case was executed.
The postcondition is part of the test case workflow. The manual tester has to confirm whether or not the postcondition has been fulfilled. 6. Select New test step to add multiple steps to your test case. The steps details are saved automatically.
Copying clipboard values
When you add steps to a test case, you can enter any string value (e.g. {CLIPBOARD}) in the Clipboard data field.
During, a pop-up window shows the test case execution steps. The string value has been replaced by the Clipboard data value and placed in the Windows Clipboard.
Setting test execution results
When you manually execute a test case, you can set the results as Failed or Passed. For test cases with multiple steps, you can set the result for individual steps by selecting Set Failed, Set Passed, or Set Passed Till Here for all steps. To leave notes, use the Tester comment section.
Debugging
You can debug manual test cases to set the result of each step, by opening a test case and navigating to Tasks > Debug.