test-manager
latest
false
Test Manager user guide
- 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
- 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
- Creating automated tests
- Executing performance scenarios
- Known limitations for performance testing
- Best practices for performance testing
- Troubleshooting performance testing
- Accessibility testing for Test Cloud
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Coding Agents for Testing
- Troubleshooting
Best practices for performance testing in Test Manager: ensure test stability, use gradual ramp-up, and prepare parametrized datasets before scaling.
Design reliable test automations
Ensure test cases are robust, data-stable, and free from flakiness before scaling.
Choose ramp-up and duration strategies
Use gradual ramp-up to simulate realistic traffic and avoid unrealistically long or short peak phases.
Handle test data at scale
Prepare parametrized datasets (via Data Fabric) to avoid duplicate inputs that could skew results.
Avoid common pitfall
- Ensure there are sufficient infrastructure resources.
- Validate tests locally before publishing.
- Use the latest package versions.
Two more habits worth adopting
- Complete proof of concept (POC) Success Criteria intake before starting a new engagement, so the team agrees up front on what "passing" performance actually means for this application.
- Run Workflow Analyzer and, for on-premises robots, Capacity Planner before scaling up a scenario — catching an unsupported activity or an under-provisioned machine during dry run is far cheaper than discovering it mid-run at full load.