Free tools Windows power users keep installed
One-click scans. No signup required.
To integrate automated testing with qTest, first enable Automation Integration in the target project and map the test framework’s result statuses to qTest statuses. Then choose where tests will run: on qTest-managed Automation Host machines, in Jenkins or Bamboo with results sent back to qTest, or in a custom workflow using Universal Agent or the qTest APIs.
The key distinction is that the Jenkins and Bamboo integrations collect and submit results; they do not execute tests. Choose a route based on who should run the tests, the report format and parser you can provide, your scheduling needs, and the features available in your qTest deployment. Tricentis documentation and package entitlements can vary by release and between SaaS and on-premises installations, so check the documentation for your instance.
As an Amazon Associate I earn from qualifying purchases.
Choose where automated tests will run
| Route | Where tests execute | Best fit | Important consideration |
|---|---|---|---|
| qTest scheduling / Launch | On machines with a registered Automation Host and agent | Teams that want to schedule automation through qTest and review jobs there | Activate project integration, map statuses, register a host and agent, then create and schedule test runs. Framework support depends on the selected agent. |
| Jenkins or Bamboo integration | In the CI server’s build | Teams already running tests in CI that want results associated with qTest | The integration collects results rather than running tests. The documented report format is JUnit XML. |
| Universal Agent | In a scripted workflow on the agent host | Teams using custom or varied frameworks with explicit setup, checkout, execution, and reporting steps | The Universal Agent overview specifies Automation Host 2.1.0 or later. Check the current parser and agent instructions for your deployment. |
| qTest APIs | In an external runner or custom integration | Teams needing bespoke result submission or integration logic | Enable project Automation Integration, use HTTPS API resources, and handle authentication and status mapping. |
Before choosing, confirm the execution owner, report format and parser support, status mappings, framework support, scheduling needs, required permissions, deployment model, and current license entitlement. Tricentis documentation describes Tosca DEX as the native Tosca execution route in qTest Launch; non-Tosca runs are distributed across selected agents. A Launch quick start guide describes Launch availability as limited to the Elite package, but verify the entitlement for your current contract and deployment.
Prepare the qTest project first
- Open Automation Settings for the target project. Activate Automation Integration. A Project Admin is required to change these settings.
- Map source statuses to qTest statuses. Map every status your framework or CI report can send, including pass, fail, skipped, and any framework-specific states, to the intended qTest Manager values. Do not assume the names match.
- Save and confirm the target project. Results must be sent to the intended project, release, and test cycle. Confirm these associations as part of a representative run.
For CI integrations, activate CI Tool Integration for each qTest project that should receive results. Tricentis documentation says this also activates Automation Integration; still review the status mapping before sending results.
Run tests on qTest-managed hosts and agents
Use qTest Test Automation Scheduling or Launch when you want qTest to schedule work on machines that run registered Automation Host software and agents. The agents poll for scheduled work, execute the automation, and send logs and results back to qTest Manager.
- Install Automation Host. Download and install it on each machine that will run tests. When running, the host registers with qTest.
- Create an Automation Agent in qTest Launch. Select an agent and workflow that support your framework. Use Universal Agent when you need a scripted workflow for a custom framework.
- Create automation test runs in qTest Manager. Ensure they are associated with the intended project, release, and test cycle.
- Schedule the test runs. The agent polls the schedule, runs the automation, and returns logs and results to qTest Manager.
- Review the schedule and execution logs. Use the relevant qTest scheduling or Launch views, then confirm returned statuses and test associations.
Framework and custom-run support depends on the selected agent and available integrations. Check the instructions for the agent and the qTest release in use rather than assuming every framework is supported.
Send Jenkins or Bamboo results to qTest
In this pattern, Jenkins or Bamboo runs the tests. The qTest integration collects and submits the resulting report so the execution can be associated with qTest. Tricentis’ Jenkins and Bamboo integration documentation specifies JUnit XML as the supported report format.
- Enable CI Tool Integration in the qTest project. Map the CI result statuses to qTest values in Automation Settings.
- Install the relevant qTest plugin. Follow the current Jenkins or Bamboo integration instructions for your qTest deployment and plugin version.
- Configure the qTest connection. Obtain the appropriate integration or API token from qTest resources. Store it in the CI system’s credential-management feature rather than embedding it in a job script or source repository.
- Keep test execution in the CI job. Configure the job to produce JUnit XML for the qTest plugin to collect. Jenkins users can use the xUnit plugin to publish JUnit XML-compatible results when their framework does not produce that format directly.
- Run a representative build and verify the result. Check that the expected test runs, statuses, and logs appear in qTest Manager and belong to the intended project and test cycle.
The documented qTest Bamboo plugin does not support Bamboo Specs. If your Bamboo configuration depends on Specs, verify a compatible integration path before building around the plugin.
Connect a custom framework with Universal Agent
Universal Agent is intended for scripted workflows where you control the setup and reporting steps. The documented workflow is to prepare the execution environment, obtain the source code, execute the tests, and submit results to qTest Manager.
- Check the host version. The Universal Agent overview specifies Automation Host 2.1.0 or later.
- Prepare the agent environment. Install the tools, dependencies, and framework needed to run the tests on the host.
- Obtain the test source. Configure the workflow to retrieve the required source code.
- Run the tests and produce results. Follow the parser and framework integration instructions for the workflow you selected.
- Submit the results to qTest Manager. Confirm that the parser recognizes the report and that returned statuses map correctly in the project.
Tricentis’ Universal Agent overview points to instructions for agent creation, framework integration, code snippets, parsers, and custom parser development. Follow the instructions matching the installed host and qTest release.
Rank #4
Build a direct integration with qTest APIs
Use the API route when an external runner or internal service needs custom control over result submission. qTest API resources use HTTPS request URIs, standard request methods, headers, and request bodies. The API specifications describe authentication with a qTest authentication token.
Recommended Free Tools
- Enable Automation Integration in the project. Automation parameters are invalid when Automation Settings are disabled.
- Consult the API specification for your qTest release and deployment. Confirm the resource endpoints and request schema before implementing calls.
- Authenticate with a qTest token. Protect the token as a credential and use HTTPS.
- Send result data using the documented resource and schema. Include the test and execution context required by the endpoint and map statuses to the project’s configured values.
- Verify the submitted execution in qTest Manager. Check its status, logs or report details, and project/release/test-cycle association.
Do not assume an API route or payload from one qTest release or deployment applies unchanged to another. Use the specification for the target instance.
Best Value
Troubleshoot common integration failures
- No results arrive from Jenkins or Bamboo: verify that the plugin is configured for the intended qTest project, the job produced JUnit XML, and the plugin can read the report path.
- Results arrive with unexpected statuses: review Automation Settings and explicitly map the source statuses, including skipped or framework-specific values.
- Authentication stops working after a password reset: Tricentis’ qTest resources documentation says API, Jenkins, and Bamboo integration tokens automatically expire when a user password is reset. Recheck the applicable token and update the CI credential or integration configuration.
- An agent does not pick up scheduled work: confirm Automation Host is installed and registered, the agent is configured in Launch, and the test run was actually scheduled.
- Universal Agent cannot parse a report: check the parser and framework instructions for the installed version; custom frameworks may need a custom parser.
- API automation parameters are rejected: ensure Automation Integration is enabled in the project and compare the request with the API specification for the target release.
- A documented feature is unavailable: verify the qTest package entitlement, installed version, and whether the instance is SaaS or on-premises. Documentation and contract availability can differ.
Or skip the browser setup
For a website screenshot needed alongside test evidence, ScreenshotNeo offers a single GET request for a screenshot or PDF. Its capture flow accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; individual cleanup steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. ScreenshotNeo also has an MCP server with tools for AI agents, including Claude, Cursor, and other MCP clients.
Example cURL request for a WebP screenshot:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for options and setup. The service includes 1,000 screenshots a month free with no card; paid plans start at $5 for 3,000. Sign up for the free plan.
Frequently Asked Questions
Can qTest run automated tests?
Yes, through Automation Host and agents that poll scheduled work and execute it on their machines. If tests already run in Jenkins or Bamboo, the qTest integrations collect the CI results rather than running those tests.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Can I send results from a framework that does not generate JUnit XML?
For Jenkins, the documented option is to use the xUnit plugin to publish JUnit XML-compatible results. For custom workflows, investigate Universal Agent’s parser instructions or use a direct API integration designed for the target qTest release.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
