🪝

CI/CD - Webhook Configuration

How to set up and run DoesQA in a CI/CD pipeline, and the configuration options available
In order to get started, you will need to sign into your DoesQA account. Once in the app, head to Settings ( bottom of the menu ) and into Webhooks.
From here, you are able to Create and Delete webhook keys.

Creating a new key

To create a new key, from the settings menu click on the + icon at the top.
A modal will appear and give you the following:

Name

Use this field to identify the token, this will be visible instead of the user that triggered the run. An example would be "CI - Staging"

Slack Channel

If you have installed our Slack integration, then from here you will be able to pick a channel for the test reports to go to. This is handy if you have a different channel for different environments. By default, these will go to the original channel that you picked when you integrated slack

Webhook Key

This is your secret key, only displayed once - so please store this in a safe place. You will need this key in order to authenticate requests coming into our APIs.

Crafting a webhook call

To trigger test runs remotely, you need to POST to our API. Your ACCOUNT_ID is located on the settings page. Alternatively, you can also do a GET, see the API options below.
get
https://app.does.qa/api/hook
/ACCOUNT_ID
Preview tests before integrating the hook into your pipelines
post
https://app.does.qa/api/hook
/ACCOUNT_ID
Trigger DoesQA tests externally from the UI
For any additional assistance in setting up your webhooks, please reach out to support and we would be more than happy to assist!