> ## Launching tests

> How to launch Antithesis tests.

> Fetch the complete documentation index at: https://antithesis.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

---

Once you've [written a test](/docs/product/writing_tests/), 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

## Product surfaces

**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](/docs/reference/webhook/webhook_reference/). Clicking on a test launcher opens a dialogue box with the available parameters for that test.

You must provide values for parameters in the main dialogue in order to launch the test. Less frequently used parameters are hidden in fold-down menus. All parameters come with sensible default values pre-filled where possible.

If you'd like to receive the [triage report](/docs/product/understanding_test_results/reports/) by email, make sure to specify a report recipient -- the report is always accessible in the web app.

![Illustration 0](./images/launcher_dialogue.png)

You can also configure a test in the launcher, then copy the webhook code 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](/docs/product/writing_tests/controlling_faults/).

Your Antithesis team can help you with this process. Please contact us at support@antithesis.com or [ask on our Discord](https://discord.com/invite/antithesis).

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](/docs/reference/rest_api/#tag-launch) endpoint lets you configure test parameters and start a test run programatically.

**Through your CI**

Antithesis integrates natively with [GitHub Actions](https://docs.github.com/en/actions) through the [Antithesis Trigger Action](https://github.com/antithesishq/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](https://github.com/antithesishq/antithesis-trigger-action/blob/main/README.md) to step it up.

**With Snouty CLI**

Install [Snouty CLI](/docs/ai/snouty/), then run [`snouty launch`](/docs/ai/snouty/#launch-a-test-run) to push your container images and start a test run.

## What's next

Once your test is running, Antithesis will setup and explore your system for the configuration duration of time. You can look at the logs stream in with the [logs explorer](/docs/product/understanding_test_results/logs_explorer/). Once complete, Antithesis generates a [triage report](/docs/product/understanding_test_results/reports/) summarizing the test results. [Understand your test results](/docs/product/understanding_test_results) gives you several surfaces to consume your test results.