test-manager
latest
false
Test Manager user guide
- Getting started
- Project management
- 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
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Enabling or disabling governance in bulk for test cases
- Enforcing signing order for governed test cases
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Viewing governance information for test case logs
- Managing approvers for governed test case logs
- Managing governed test case logs in the In Work state
- Managing governed test case logs in the In Review state
- Managing governed test case logs in the Signed state
- Managing comments for governed test case logs
- Enabling governance at test case log level
- Disabling governance at test case log level
- Viewing and searching test cases
- Project operations and utilities
- Test Manager settings
- Tenant level settings
- General project settings
- Events
- Subscribing to events
- Subscribing to all events
- Unsubscribing from events
- Unsubscribing from all events
- Unsubscribing from the Notifications settings page
- Viewing notifications
- Filtering notifications
- Viewing email notifications
- Enabling email notifications for SMTP servers
- Viewing only unread notifications
- Marking all notifications as read
- Clearing all notifications
- Deleting notifications
- Customer managed keys encryption
- Audit logs
- ALM tool integration
- ALM tool integration
- Test Manager Connect
- Test Manager - Integration Service connector
- Outbound IP ranges for connectors
- Working with SAP Cloud ALM and Test Manager
- Step 1: Integrating SAP Cloud ALM with Test Manager
- Step 2: Creating automated test cases in SAP Cloud ALM
- Step 3: Creating automated test cases in Test Manager
- Step 4: Synchronizing test cases from Test Manager to SAP Cloud ALM
- Step 5: Assigning test automations to test cases
- Step 6: Executing test cases
- SAP test automation best practices
- Troubleshooting the Jira integration
- API integration
- Coding Agents for Testing
- Troubleshooting
Adding manual steps to a test case
Add preconditions, descriptions, expected behavior, clipboard data, and postconditions to manual test steps in Test Manager.
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:
Prerequisites
A project in Test Manager. If you do not have a project yet, see Creating a Project.
Steps
-
Open your project in Test Manager.
-
In the left navigation panel, go to Test Cases.
-
Select the test case key to open it.
-
Go to Manual Steps and select 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 (for example,
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. Clipboard data can also be set or updated programmatically through the Test Manager Model Context Protocol (MCP) tools (Bulk add test steps, Bulk update test steps) — for example, when generating test cases through Autopilot chat (agent) or Delegate. (For Cloud Commercial and Cloud Public Sector only) The character limit for the Clipboard data field is 8000 characters.
- 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.
Note:- Consider adding a single action for each step.
- To duplicate, delete and reposition the steps, select 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
-
Select New test step to add multiple steps to your test case.
Result
The manual steps are added to the test case and saved automatically. The test case is ready for manual execution, with preconditions, step descriptions, expected behaviors, and postconditions visible to the tester.