Launching tests
Once you’ve written a test, you’re ready to run it. Antithesis gives you several ways to launch a test:
- from the web app
- with the API
- through your CI
- with the Snouty CLI
Choose a performance tier
Antithesis lets you choose a performance tier when launching a test run. Higher performance tiers explore system states faster through increased parallelism, and so consume core hours faster. You can track your core hour usage in the web app.
Antithesis provides three performance tiers:
- Standard
- Fast
- Turbo
You can configure the performance tier when you launch a test.
Launch methods
From the web app
In the web app, the Test launchers tab lets you configure test parameters and launch a test.
Configuring test parameters
Antithesis tests are all configurable using a standard set of parameters. Clicking on a test launcher opens a dialogue box with the available parameters for that test.
The main dialogue includes parameters that you must provide in order to launch the test, such as test duration, performance tier, and your config image. Optional parameters are hidden in fold-down menus. All parameters come with sensible default values pre-filled where possible.
To check your setup before running a full test, check the Setup mode option.
If you’d like to receive the triage report by email, make sure to specify a report recipient — the report is always accessible in the web app.
If you’d rather run a webhook, you can configure a test in the launcher, then select Webhook to copy the webhook curl command with one click.
Creating new tests
Every Antithesis tenant comes with several pre-written tests.
New tests can be added to customize elements like the hostility of the test environment, which containers are exposed to faults, or the types of faults injected.
Your Antithesis team can help you with this process. Please contact us at support@antithesis.com or ask on our Discord.
Once the test is created, you’ll be able to configure and launch it with a test launcher.
With the API
The Launch a test run endpoint lets you configure test parameters and start a test run programmatically.
Through your CI
Antithesis integrates natively with GitHub Actions through the Antithesis Trigger Action. You can easily trigger a test run through your workflow and have the results reported back natively in GitHub. Follow the README to set it up.
With Snouty CLI
Install Snouty CLI, then run snouty launch to push your container images and start a test run.
What’s next
Once your test is running, Antithesis will set up your system and explore it for the duration that you configured (minimum 15 minutes). Note that this is minutes of test time — the test run itself will last longer because it also includes set up and build time.
During the test run, you can watch the logs stream in with the logs explorer. Once the run is complete, you can view the triage report summarizing the test results.
See Understand your test results for more ways to explore your test run.