Overview

Send Tesults test results to Callgoose SQIBS. Tesults posts a message card to a Microsoft Teams style webhook every time new results arrive, and you give it your SQIBS API endpoint instead of a Teams URL. SQIBS opens an incident for each run, titled with the target and pass rate.

You need
A Tesults project you administer, and a SQIBS API token
Setup time
About 5 minutes
Result
Test runs open SQIBS incidents

How it works

Tesults
Alert fires
A test run uploads new results.
Tesults
Sends a webhook
Through the MS Teams webhook, as a JSON card.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident shows the pass rate.

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. In Select Integration Template, choose Tesults. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "@type" MessageCard Opens an incident.
Title from "title" Becomes the incident title.
Description from "text" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

The template opens an incident for every run, passing or not. To page only when tests fail, add a second trigger value on "themeColor" with the colour Tesults uses for failing runs (check a failing run in the API log), or route these incidents to a low Priority service.

The template is a starting point, not a lock-in: every value stays visible and you can change it.

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: Add the webhook in Tesults

  1. In Tesults, open the configuration menu and go to Integrations, then Webhooks (MS Teams, Mattermost).
  2. Under MS Teams, choose Add a webhook and paste your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=tesults&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. Choose whether it applies to all targets or one target, and save.

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. Upload a test run to the project.
  2. In SQIBS, a new incident opens. Tesults's card looks like this (shortened):
{
  "@type": "MessageCard",
  "@context": "http://schema.org/extensions",
  "themeColor": "#f0ad4e",
  "title": "Nightly regression",
  "text": "66.67% Pass (2/3)",
  "potentialAction": [
    {
      "@type": "ViewAction",
      "name": "Results",
      "target": [
        "https://www.tesults.com/results/rsp/view/results/run/..."
      ]
    }
  ]
}

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 Tesults 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 nightly run fails, SQIBS can run a workflow that collects the test environment's logs and attaches them for the engineer.

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: