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

Settings

PreviousAlertsNextTest Plans

Last updated 2 years ago

Was this helpful?

Notification Settings

Setting Slack Member ID

You can receive slack notifications for test run status changes (when a test run gets submitted and completes) and when a team member leaves a message on a test run. You can choose to receive a notification to your email, a Slack DM or both.

Once these notifications are turned on, all manual test runs will default to that setting. You have the option to turn them off/on at the time you manually start a test run.

In Testery, go to Settings --> Profile tab. You will see the following notification settings.

Turn on email or slack notifications or both. If you turn on Slack notifications you will need to connect your Slack user to your Testery User. To do this...

  1. Ensure your Slack Workspace is authorized. In the Testery App, go to Settings > Integrations. If you see, "Authorize Slack Integration," click that and complete that process.

    • If you see "Remove Slack Integration," then you are already authorized and can move forward.

    • This only needs to be done once in your Testery account.

  2. In Slack, type the command /testery connect. Follow the prompts to complete the process and your users will then be connected.

    • Each Testery user that wants/needs Slack notifications must also use the connect Slash Command above.

If Slash commands aren't working, you may need re-install your Slack App...

  1. Go to Settings > Integrations

  2. Click the "Remove Slack Integration" button. Complete the process.

  3. Click the "Authorize Slack Integration" button. Complete the process.

These settings only apply to test runs kicked off manually. If there is a particular test run that is scheduled that you would like to follow, you would have to go into the test run once its activated and follow the test run.

Testery Notification Settings