Continuous Integration and Triggers

Each test configuration has one or more trigger URLs that can be used to trigger execution. This allows us to integrate with continuous integration platforms, schedulers, scripts, etc.

Triggers

In the above configuration we can POST https://api.testable.io/public/hgrgjtojmu to trigger execution. This URL is public so make sure you only give it out to trusted sources! A test configuration can have more than one trigger and each trigger can be deleted at any time. So if a trigger is compromised, simply delete it, and create a new one.

Triggers and Script Params

Node.js, PhantomJs/SlimerJs, Gatling, and Jmeter scripts all support script parameters.

You can override or add additional script params when calling the trigger URL in two ways:

  1. Query params. Example POST https://api.testable.io/public/abcdefg?myparam=myval. Any param specified here will override the same key specified in the body or the test configuration
  2. Request body. The body of the POST request can contain a JSON object with additional params. Parameters specified this way override any test configuration parameter with the same key but not a query param. An example body:
{ 'myparam2': 'myval2' }