Ask the Community
Link CI/CD results with manual testing
A typical testing strategy likely includes both manual testing and automated CI/CD pipelines. A common goal is to view these results in a unified way to determine release readiness.
This guide covers how to map automated results to your existing test cases, handle logs, and organize manual and automated runs into a single view.
Before you begin, understand how Test Management organizes manual and automated test data.
| Concept | Description |
|---|---|
| Test Run | A container for results from a single source (either manual or automated). You cannot merge automated results into a manually created run. |
| Test Plan | A parent container that aggregates multiple test runs (both manual and automated test runs) into a single dashboard. |
| Tagging | The method of linking an automated test back to a specific Test Case ID in the repository. |
Test Management processes uploads as follows:
- Separation of test runs: The system treats manual test runs and automated test runs as distinct entities. When you upload a JUnit XML file (or use the SDK), the system automatically creates a new Automation Test Run.
- No direct merge: You cannot append automated results directly into an existing manual test run.
To track your manual and automated tests together, use test plans.
Map automation results to test cases
To link your automated results to specific Test Cases in the Test Management repository, you must tag your automation code.
If you do not tag your tests, the system cannot identify them. It will create new, unmapped orphan test cases for every execution, cluttering your project.
- How to tag: Add the Test Case ID (e.g., TC-101) directly to your test method name or description in your code.
Configure logs in JUnit XML
To view logs in the Test Management dashboard, your test runner must write them into the XML report. Ensure your test runner outputs logs to the
You can only upload one XML file per build. External log files are not supported.
Example:
<testcase classname="Cart" name="verifyLogin_TC_101">
<system-out>
[INFO] Button Clicked
[INFO] API 200 OK
</system-out>
</testcase>
Upload results via CLI
Once your pipeline generates the XML, use the CLI to upload it. This action automatically creates a new Automated Test Run. Refer to how to upload test data from reports using CLI documentation.
Unify in a test plan
Now that you have a manual test run and an automated test run (created via the CLI upload), you can group them.
- Navigate to Test Plans in the dashboard.
- Create or open a test plan.
- Add test runs to the test plan.
- Select your manual test run and your automated test runs.
You now have a unified dashboard showing aggregate pass/fail rates and coverage across both manual and automated testing.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!