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 to Know Testery

Test Runs

PreviousDashboardNextTest Selection Rules

Last updated 4 months ago

Was this helpful?

The Test Runs view shows a list of your most recent test runs. You can filter by Date, Project, Environment, or Status to find the test run you're looking for.

Test Run Status and Test Status

There are two kinds of statuses in Testery:

  1. Test Run Status - the status of the entire test run regardless of how many tests are in it

  2. Test Status - the status of a single test within a test run

Test Run Statuses

Status

Description

SUBMITTED

Test run has been submitted to the queue to be run

QUEUED

Waiting for another test run in the same environment to finish. We do not run 2 test runs in the same environment at once.

RUNNING

Test run is currently running

PASS

All tests that are not ignored passed.

FAIL

There was at least one test in the test run that failed OR an error occurred and the test run can’t finish. If the latter happens a failure reason should display.

CANCELED

  1. Test run was manually canceled by someone. (user’s username will display to show who canceled the test run) OR

  2. Test run will be automatically canceled if it runs for more than 3 hours (message will be Canceled - Due to running too long) OR

  3. Test run is in queued status and a newer test run comes in, the current queued test run will be canceled (message will be Canceled - Due to newer test run)

Test Statuses

Status

Description

The test passed.

The test failed.

Test was flagged as ignored and this test did NOT run.

Test is waiting to run.

Test is running.

Test Run Options

There are 4 options for define the tests that will be executed during your test run.

Run all tests in project - All tests detected in the project will be executed.

Select test suite - Tests will be determined by a predetermined test suite.

Filter tests in project - A one-time set of filters will be applied. These can be done with include/exclude tags or by test file filters.

PASS

FAIL

IGNORED

PENDING

Use testery.yml - Test selection will be controlled by the rules in the testery.yml file.

Read here for details on how to define these rules.