- 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
Re-running only failed test cases
Re-run an individual failed test case in an ordered test set by disabling enforced execution order.
There is no bulk option to re-run only the failed test cases in an ordered test set. You can re-run an individual failed test case after execution.
Context
Enforcing an execution order and re-running individual test cases are mutually exclusive. A partial re-run produces results that appear to have run in order when they did not. This behavior is by design.
When Enforce Execution Order is turned off, you cannot control the execution order of the re-run test cases, unless you run the test cases one by one. As an alternative, trigger individual test case executions through the API.
To reduce the impact of this limitation, design independent test cases. When test cases depend on intermediate outputs, store and read those outputs through a common data source. Use one of the following:
- A data table
- A file
- A queue
Steps
- Turn off Enforce Execution Order for that test set.
- Re-execute the specific test case from the Results tab.
Result
The test case re-executes individually from the Results tab, without re-running the other test cases in the ordered test set.