- 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
When you execute tests and use testing artifacts, you should be aware of their default data retention policies.
Test Data Retention – breaking changes
The Test Data Retention policy, which enforces the retention period for test results and their artifacts, will change starting with August 1, 2026.
Currently, we enforce the following data retention periods.
| Objects | Data retention period |
|---|---|
| Robot logs | 30 days |
| Other testing artifacts (test results, assertions, assertion screenshots, activity coverage, attachments) | Indefinite |
Starting with August 1, 2026, the data retention period will no longer be indefinite for the following test execution artifacts: test results (test case logs, test step logs, assertions) and execution attachments.
The data retention period of execution artifacts is counted from the creation date of a test execution. The table below details the new data retention period for each platform tier.
| Platform tier | Test Execution Artifacts Retention Period |
|---|---|
| Free | 12 months |
| Basic Trial | 12 months |
| Basic | 12 months |
| Standard Trial | 24 months |
| Standard | 24 months |
| Enterprise | 48 months |
| Application Testing Standard Trial | 48 months |
| Application Testing Standard | 24 months |
| Application Testing Enterprise | 48 months |
The current Test Data Retention policy does not impact the following test business objects, which are stored indefinitely: Test Cases, Requirements, Test Sets.
What does this change mean for you?
- Test Data Retention – cut-off date
- The new Test Data Retention policy will be enforced on August 1, 2026.
- What can I do before the Test Data Retention cut-off date?
- If you have test results and associated artifacts which exceed the new Test Data Retention period on the cut-off date, ensure you use the Export Project capability to download and store these assets to a location of your choice.
Moving forward, will I get a warning that I am approaching the end of my test data retention for an artifact?
Yes, a warning will be shown <30 days before your testing artifacts are no longer available, instructing you to download them.
What happens if I did not manage to export my test data before the retention period expires?
We strongly encourage you to download the testing artifacts you need before the cut-oof date. However, a one-time, limited and discretionary extension can be granted, if you submit a support ticket.
What happens to my data if my license expires?
If your license expires, a 12-month test data retention policy applies.