Testery Docs
TesteryFeaturesPricingRelease Notes
  • Testery Documentation
  • Release Notes
  • Get Started
    • Getting Started Guide
      • Create a Testery Account
      • Configure Your Project
      • Run Your Tests
      • Configure Slack Alerts
      • Schedule Your Test Runs
      • Invite Your Team
      • Get More From Testery
  • Get to Know Testery
    • Dashboard
    • Test Runs
      • Test Selection Rules
    • Projects
    • Test Triggers
    • Environments
    • Alerts
    • Settings
    • Test Plans
    • Test Stacks
      • Python
      • Node.js 16 End of Life
      • Default Chrome Version Change
      • Python 3.8 End of Life
    • Deployments
    • System Variables
    • Tags
    • Screenshots
    • Uploading Test Artifacts to Testery
    • Setting Test Execution Priority
    • Setting the Number of Parallel Tests
  • Integrate with Testery
    • Built-In Integrations with Testery
      • Jira
      • Slack
    • CI/CD Integration Guides
      • Azure Devops Pipelines
      • Set Up CircleCI to Run Testery Tests
      • Jenkins
      • GitHub Actions
      • Octopus Deploy
      • TugboatQA
    • Testery CLI
    • Testery REST API
      • Testery REST API Resources
    • Microsoft Teams
  • Framework-specific Guidance
    • Supported Testing Frameworks
    • Cypress
      • Updating Cypress Tests to Output in JUnit XML Format
    • Playwright
      • Update Playwright Tests to Output in JUnit XML Format for Import Into Testery
    • PyTest
      • Update Pytest to Generate JUnit XML for Import into Testery
    • TestNG
      • Updating TestNG Tests to Output in JUnit XML Format
  • How-To
    • Enable or Disable Automatic Rerunning of Tests
    • Run Cypress Tests without Connecting Repository
    • How to Store Sensitive Data Like Username and Password For a Cypress Test
    • Connect to a Private npm Repository
    • Running Scripts Before the Tests
    • Upload Test Run for Analysis
  • MISC
    • Troubleshooting Steps
  • Fixing Tests
    • Fix Common Selenium Exceptions
      • Fix a ChromeDriver Version Exception
      • Fix a NoSuchElement Exception
      • Fix a TimeoutException
      • Fix an ElementNotVisibleException
      • Fix a StaleElementReferenceException
      • Fix a WebDriverException
      • Fix an InvalidArgumentException
      • Fix a NoSuchWindowException
      • Fix an UnhandledAlertException
      • Fix an InvalidSelectorException
Powered by GitBook
On this page

Was this helpful?

  1. Integrate with Testery
  2. CI/CD Integration Guides

Octopus Deploy

PreviousGitHub ActionsNextTugboatQA

Last updated 4 years ago

Was this helpful?

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.

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.

  • Set Git Reference to the commit hash of the repository that includes the version of the tests you want to run.

  • 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.

Set Testery Project Name to match the name of your in Testery.

Set Testery Environment to match the name of your 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 . 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 .

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

Project
Environment
Tags
uploading test artifacts to Testery
https://octopus.com/docs/octopus-rest-api/octopus-cli/build-information