test-suite
latest
false
- Getting Started with Test Suite
- Studio
- Orchestrator
- Testing robots
- Test Manager
- Change Impact Analysis
- Requirements
- Assigning test cases to requirements
- Linking test cases in Studio to Test Manager
- Unlink automation
- Delete test cases
- Document test cases with Task Capture
- Create test cases
- Importing manual test cases
- Generate tests for requirements
- Cloning test cases
- Exporting test cases
- Automate test cases
- Manual test cases
- Applying filters and views
- Test sets
- Executing tests
- Documents
- Reports
- Export data
- Bulk operations
- Searching with Autopilot
- Troubleshooting
Test results
Test Suite User Guide
Last updated Nov 20, 2024
Test results
When you start executing a test set, Test Manager goes through the following process:
- A Test Execution is created in the Execution section of Test Manager. This serves as the container for the test results.
- For every test case within the executed test set, an empty Test Case Log is generated. This log is attached to the Test Execution and will hold its associated test results.
- As the execution continues, the Test Manager fills each Test Case Log with results and related log information.
Note: Every time a test execution is created, Test Case Logs for
all associated test cases from the original test set are added. Furthermore, dynamic
assignments are resolved at this stage. This means existing Test Executions remain
consistent, regardless of updates or deletions made to the original test set.
The chart below illustrates the process of executing a test set in Test Manager.
As a consequence, after a test set has been executed, any changes to the test set or its associated test cases do not affect the results from previous executions. Even when a test set is deleted, all the test executions remain unchanged.
Who can see projects
All user roles can see test results.
For more information see User and Group Access Management.