> For the complete documentation index, see [llms.txt](https://docs.testery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testery.io/integrations/ci-cd-integration-guide/octopus-deploy.md).

# Octopus Deploy

#### Step 1. Upload Test Artifacts to Testery

#### Step 2. **Add the** Testery - Create Test Run step to your process.

* Select **Deployments → Process → Add Step.**
* Search for "testery". Install and add the **Testery - Create Test Run** step.

<div align="left"><img src="/files/-MK5fraCdgUHoVnSqOhQ" alt=""></div>

**Step 3. Configure the create test run step.**

* Set **Testery Token** to your Testery API Token. To retrieve your Testery token, click **Settings → Integrations → Show API Token** and copy the token that is displayed. Keep this token secure as it allows access to Testery on your behalf.

![](/files/-MK5gKPZRhMDojZLaxJL)

* Set **Testery Project Name** to match the name of your [Project](/get-to-know-testery/projects.md) in Testery.
* Set **Testery Environment** to match the name of your [Environment](/get-to-know-testery/set-up-your-test-environments.md) in Testery. It is common when integrating with Octopus Deploy to have the name of the Testery environment match either your Octopus Deploy environments or tenant names. In these cases you may want to use an Octopus system variable such as `#{Octopus.Environment.Name}`.
* Optionally set **Testery Include Tags** to run a specific set of [Tags](/get-to-know-testery/tags.md). This is useful if you only want to run smoke tests instead of full regression, etc.
* Set **Build ID** to a unique number. This could come from your build system or from Octopus Deploy. When [uploading test artifacts to Testery](/get-to-know-testery/uploading-test-artifacts-to-testery.md).
* Set **Git Reference** to the commit hash of the repository that includes the version of the tests you want to run.

{% hint style="info" %}
You may want to get the Git Reference from a previous step's package build information. To do so, set the value to\
`#{each buildInfo in Octopus.Deployment.PackageBuildInformation}#{buildInfo.VcsCommitNumber}#{/each}`\
\
For more information about publishing build information to Octopus see <https://octopus.com/docs/octopus-rest-api/octopus-cli/build-information>
{% endhint %}

* Ignore **Testery API URL** as this is for testing purposes only.
* You may want to set conditions so that this step only runs in certain environments / situations.