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
  • Test Run
  • Environment

Was this helpful?

  1. Get to Know Testery

Alerts

PreviousEnvironmentsNextSettings

Last updated 1 year ago

Was this helpful?

Alerts enable you to notify your team (or anyone else you want) when test runs pass, fail, or complete with any status. You can send messages to various places like Slack, Microsoft Teams, OpsGenie, or even webhooks.

Specifying Criteria in Alerts

Test Run

Parameter
Data Type
Nullable

environment

projectId

Long

ended

Boolean

priority

Int

passCount

Int

failCount

Int

ignoredCount

Int

totalCount

Int

timeoutCount

Int

totalTestingTime

Int

maxRunners

Int

hasFlakyTest

Boolean

retryFailedTests

Boolean

gitRef

String

branch

String

environmentId

Long

testSuiteId

Long

statusSetByUser

Boolean

includeTags

List<String>

excludedTags

List<String>

runnerConfigurationId

Long

testFilters

List<String>

defaultToParallelizeByFile

Boolean

testTimeoutSeconds

Int

timeoutMinutes

Int

recordVideo

Boolean

Environment

Parameter
Data Type
Nullable

name

String

key

String

archived

Boolean

pipelineStageId

Long

url

String

Testery uses the syntax for defining criteria in alerts. For example, you can use environment.key=='foo' to match a specific environment or passCount < 100 or failCount > 100 The following objects/parameters are available for use in expressions:

SpEL expression language
Environment