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. Get Started
  2. Getting Started Guide

Run Your Tests

PreviousConfigure Your ProjectNextConfigure Slack Alerts

Last updated 1 year ago

Was this helpful?

In Testery, there are three ways to run your tests. You can perform one-off test runs (shown below), schedule your test runs, or integrate with CI/CD to run your tests.

For now, let's just perform a one-off test run to make sure the project is configured correctly.

  1. Click Test Runs or navigate to the page.

  2. Click New Test Run.

  3. Enter your desired parameters for the test run. Environment - This is the environment that the tests will target as the system under test. This is typically something like dev, qa, rc, or prod. See Environmentsfor more information. Trigger Type - Here you can select how you would like to start the tests. For now, just select Run tests now. Options - Options let you select what set of tests you'd like to run. You can run all the tests in a project, select individual suites, or filter tests by test name or tag.

  4. Click Run Test to start the test run.

  5. You will be taken back to the test runs page and should see your test run in a "SUBMITTED" state. Testery is now dynamically provisioning the infrastructure to run your tests.

  6. Congratulations! You have tests running on Testery! You are now ready to Configure Slack Alerts.

Everyone's test projects are a bit different and occasionally additional steps are required to configure your projects. If you need any additional assistance at this step, please email or make a request at the .

Test Runs
support@testery.io
Testery Service Desk