URL Callout Integration with Tricentis
How AutoRABIT Uses the URL Callout to Integrate with Tricentis
AutoRABIT ARM integrates with Tricentis, a leading continuous-testing platform, to streamline quality gates within CI/CD pipelines. The two systems communicate through URL callouts, which let AutoRABIT trigger automated tests and capture the results at key stages of the release lifecycle.
How URL callouts work in AutoRABIT
A URL callout is an HTTP request that AutoRABIT sends to an external service—Tricentis, in this case—when a predefined event occurs (for example, a new build, a successful deployment, or a failure that requires regression testing).
The callout allows AutoRABIT to:
Trigger automated tests – initiate Tricentis test execution as soon as a build or release package is ready.
Pass context and metadata – send the build version, target environment, and any specific test collections that must run.
Receive test results – capture Tricentis responses or callbacks so the pipeline can react immediately (e.g., promote, roll back, or notify stakeholders).
After Tricentis finishes, it returns the results through an API response or a callback URL. AutoRABIT can then notify teams (email, chat, dashboards) and log the outcome for auditing.
Benefits of the AutoRABIT–Tricentis integration
End-to-end automation – eliminate manual test hand-offs and keep the pipeline fully automated.
Targeted, timely tests – run only the suites mapped to the current build metadata, improving efficiency.
Fast feedback loops – developers see pass/fail status almost immediately, reducing late-cycle rework.
Compliance & traceability – every test run is recorded in AutoRABIT, producing a clear audit trail.
Setting up a URL callout in ARM
You can create a URL callout inside a CI Job to trigger any Tricentis (Testim Salesforce) execution—Test, Test Plan, Test Suite, or Test Label—through a single webhook. No extra VMs or intermediary CI tools are required.
1 — Create an API key
Obtain an API key from Testim Salesforce (available on Pro accounts). Copy the key immediately; it is shown only once.

2 — Copy the execution payload
Open the Testim.io Public API in Swagger. Select the remote-execution endpoint that matches what you want to run—Test, Test Plan, Test Suite, or Test Label—and copy the sample JSON payload.

3 — Configure the callout in AutoRABIT
When you create (or edit) the CI Job in AutoRABIT:
Choose the stage – decide whether the callout runs Pre-Deployment or Post-Deployment (on success or failure).
Method – set to
POST
.URL – paste the REST endpoint from step 2 and append the test entity ID, for example:
Last updated
Was this helpful?