Overview

Send failed Tricentis test runs (for example from NeoLoad or Tosca pipelines) to Callgoose SQIBS. The Tricentis product, or the CI job that runs it, posts a small JSON body to your SQIBS API endpoint. SQIBS opens an incident when a run fails and resolves it when the next run passes.

You need
A Tricentis product or CI job that can call a webhook, and a SQIBS API token
Setup time
About 15 minutes
Result
Failed runs open SQIBS incidents; passing runs resolve them

How it works

Tricentis
Alert fires
A test run ends with a failed result.
Tricentis
Sends a webhook
A webhook posts the JSON body you define.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
FAILED opens it, PASSED closes it.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add the API filter in SQIBS

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. Add a filter with these values (there is no built-in Tricentis template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "status" FAILED Opens an incident.
Resolve "status" PASSED Resolves the open incident.
Match "name" The test name ties the passing run to the failed one.
Title from "summary" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

Find the right key with the JSON key creator
In the API Integration window, click the round {} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.

Step 2: Send results to SQIBS

  1. In the Tricentis product, open its webhook or notification settings (for example the webhooks of NeoLoad Web), or add a final step to the CI job that runs the tests.
  2. Set the URL to your SQIBS endpoint and the method to POST:
https://<your-endpoint>/sqibs-api/v1/process?from=tricentis&token=<your-token>

Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.

  1. Set the body to this JSON, replacing each <...> with the product's own variable (or the CI job's value):
{
  "source": "tricentis",
  "event_id": "<run or execution id>",
  "status": "<result: FAILED or PASSED>",
  "name": "<test or workspace name>",
  "summary": "<short result text>",
  "link": "<link to the result>"
}

If your Tricentis edition cannot change the request body, keep its own payload: send one test, open it in the JSON key creator, and use its keys in the filter instead.

  1. Send it on every run end, failed and passed, so SQIBS can resolve.

Step 3: Test it

The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.

  1. Run a test that fails.
  2. In SQIBS, a new incident opens, titled with the summary.
  3. Fix the test and run it again. When the result is PASSED, SQIBS resolves the incident.

No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the webhook.

Fix known issues automatically

Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when a load test fails on a test environment, SQIBS can run a workflow that collects the application logs and restarts the environment for the next run.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.

To set it up, in the same API filter:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.

Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.

Learn more: