Publishing Test Results Directly to analytiQa (CI/CD & Other Scenarios)¶
In addition to the Jira, qTest, and Tosca extractors, you can publish test result files straight to analytiQa over HTTPS — no extractor required. Common scenarios:
- A CI/CD pipeline step that runs after your test job (Jenkins, Azure DevOps, GitHub Actions, etc.)
- A local or ad hoc test run (Selenium, Playwright, or any tool that produces JUnit/NUnit/JSON output)
- Any other system that produces test results you want in your dashboards
You'll receive your own endpoint
Your environment has its own HTTPS endpoint URL and username/password. You can see them any time through a view link to your secure credential portal: ask your Qualtiva technical contact for one. They're shown there, never sent by email. The examples below use placeholders for these — substitute your own.
Supported Formats¶
- JUnit XML results
- NUnit XML results
- JSON
Sending a Result File¶
export AQA_ENDPOINT="https://<your-instance>.analytiqa.cloud/in-http"
export USER="<provided-by-analytiqa>"
export PASSWORD="<provided-by-analytiqa>"
curl "${AQA_ENDPOINT}" -u "${USER}:${PASSWORD}" \
-H "Content-Type: application/xml" \
-H "Test-Engine-Result-Format: nunit" \
-H "Tags: selenium,regression" \
-H "aqa-team: WhiteRabbits" \
-H "aqa-application: front-end-consumer-ui" \
-H "aqa-environment: SIT" \
-H "aqa-project: ART1" \
--data @./nunit3-result.xml
Headers¶
| Header | Example | Notes |
|---|---|---|
Test-Engine |
tosca, playwright |
The tool that produced the result. Defaults to unknown if omitted. |
Test-Engine-Result-Format |
nunit, junit, json |
Format of the file body. Defaults to unknown if omitted. |
Content-Type |
application/xml, application/json |
Standard HTTP header matching your file format. |
Tags |
long-running,web,front-end |
Comma-separated free-form tags — helps you segment and filter data later. |
aqa-team |
WhiteRabbits |
Team associated with the test run. |
aqa-application |
front-end-consumer-ui |
Application under test. |
aqa-environment |
SIT |
Environment where the tests were executed. |
aqa-project |
ART1 |
Project identifier. |
Use these consistently — they become filterable fields in your dashboards, the same as any other data source.
Need Help?¶
To get your endpoint URL, username and password, ask your Qualtiva technical contact (or support@qualtiva.solutions) for a view link to your secure credential portal. The credentials are shown there, not sent by email. See Providing Configuration & Credentials Securely.
If a result file isn't showing up as expected, see Support & Troubleshooting.