# Testery Docs ## Testery Docs - [Testery Documentation](https://docs.testery.io/readme.md): Testery is a cloud-based, continuous testing platform that makes it easy to run tests quickly and reliably and push your test results to the platforms your team uses daily. - [Release Notes](https://docs.testery.io/release-notes.md) - [Getting Started Guide](https://docs.testery.io/get-started/getting-started-guide.md) - [Create a Testery Account](https://docs.testery.io/get-started/getting-started-guide/create-an-account.md): A free Testery account will enable you to run your smoke tests on a schedule or every commit and send notifications to Slack, OpsGenie, or wherever else you need them. - [Configure Your Project](https://docs.testery.io/get-started/getting-started-guide/configure-your-project.md) - [Run Your Tests](https://docs.testery.io/get-started/getting-started-guide/run-your-tests.md) - [Configure Slack Alerts](https://docs.testery.io/get-started/getting-started-guide/configure-slack-alerts.md) - [Schedule Your Test Runs](https://docs.testery.io/get-started/getting-started-guide/schedule-your-test-runs.md) - [Invite Your Team](https://docs.testery.io/get-started/getting-started-guide/invite-your-team.md): Add users to your team by selecting Settings -> Team. - [Get More From Testery](https://docs.testery.io/get-started/getting-started-guide/create-schedules.md) - [Dashboard](https://docs.testery.io/get-to-know-testery/dashboard.md) - [Test Runs](https://docs.testery.io/get-to-know-testery/test-runs.md) - [Test Selection Rules](https://docs.testery.io/get-to-know-testery/test-runs/test-selection-rules.md) - [Projects](https://docs.testery.io/get-to-know-testery/projects.md) - [Test Triggers](https://docs.testery.io/get-to-know-testery/schedules.md) - [Environments](https://docs.testery.io/get-to-know-testery/set-up-your-test-environments.md) - [Alerts](https://docs.testery.io/get-to-know-testery/alerts.md) - [Settings](https://docs.testery.io/get-to-know-testery/settings.md) - [Test Plans](https://docs.testery.io/get-to-know-testery/test-plans.md): Test plans in Testery allow you to create a plan where you can lay out the stages of testing, specify what tests or test suites will be in each stage, what environments the test should run in, etc. - [Test Selection](https://docs.testery.io/get-to-know-testery/test-selection.md) - [Test Stacks](https://docs.testery.io/get-to-know-testery/test-stacks.md): Managing your dependencies with Test Stacks - [Python](https://docs.testery.io/get-to-know-testery/test-stacks/python.md): How to choose which version of Python to use on your runners - [Node.js 16 End of Life](https://docs.testery.io/get-to-know-testery/test-stacks/node.js-16-end-of-life.md): Handling the Upgrade to Node 18 - [Default Chrome Version Change](https://docs.testery.io/get-to-know-testery/test-stacks/default-chrome-120.md): Handling the Upgrade to Chrome 120 - [Python 3.8 End of Life](https://docs.testery.io/get-to-know-testery/test-stacks/python-3.8-end-of-life.md) - [Deployments](https://docs.testery.io/get-to-know-testery/deployments.md) - [System Variables](https://docs.testery.io/get-to-know-testery/system-variables.md) - [Tags](https://docs.testery.io/get-to-know-testery/tags.md) - [Screenshots](https://docs.testery.io/get-to-know-testery/screenshots.md) - [Uploading Test Artifacts to Testery](https://docs.testery.io/get-to-know-testery/uploading-test-artifacts-to-testery.md) - [Setting Test Execution Priority](https://docs.testery.io/get-to-know-testery/setting-test-execution-priority.md) - [Setting the Number of Parallel Tests](https://docs.testery.io/get-to-know-testery/setting-the-number-of-parallel-tests.md) - [Built-In Integrations with Testery](https://docs.testery.io/integrations/built-in-integrations-with-testery.md) - [Jira](https://docs.testery.io/integrations/built-in-integrations-with-testery/jira.md): Testery's built-in Jira integration allows user to create stories for errant tests and bugs found while testing. Stories can be tied to individual or groups of tests. - [Slack](https://docs.testery.io/integrations/built-in-integrations-with-testery/slack.md) - [CI/CD Integration Guides](https://docs.testery.io/integrations/ci-cd-integration-guide.md) - [Azure Devops Pipelines](https://docs.testery.io/integrations/ci-cd-integration-guide/azure-devops-pipelines.md) - [Set Up CircleCI to Run Testery Tests](https://docs.testery.io/integrations/ci-cd-integration-guide/circleci.md): How-to trigger a Testery test run from a CircleCI build. - [Jenkins](https://docs.testery.io/integrations/ci-cd-integration-guide/jenkins.md): Configure Jenkins in minutes to run your end-to-end tests concurrently via Testery Cloud - [GitHub Actions](https://docs.testery.io/integrations/ci-cd-integration-guide/github-actions.md) - [Octopus Deploy](https://docs.testery.io/integrations/ci-cd-integration-guide/octopus-deploy.md) - [TugboatQA](https://docs.testery.io/integrations/ci-cd-integration-guide/tugboatqa.md): Using Tugboat and Testery is one of the coolest, easiest, and fastest ways to run your E2E Cypress tests on every PR. Follow these four steps and in about 10 minutes, you'll have Cypress tests running - [Testery CLI](https://docs.testery.io/integrations/testery-cli-docs.md) - [Testery REST API](https://docs.testery.io/integrations/testery-rest-api.md) - [Testery REST API Resources](https://docs.testery.io/integrations/testery-rest-api/testery-rest-api.md): A description of the available Testery REST API end points. - [Microsoft Teams](https://docs.testery.io/integrations/microsoft-teams.md) - [Testery MCP Server](https://docs.testery.io/integrations/testery-mcp-server.md) - [Claude Plugin](https://docs.testery.io/integrations/testery-claude-plugin.md) - [Supported Testing Frameworks](https://docs.testery.io/framework-specific-guidance/supported-testing-frameworks.md) - [Cypress](https://docs.testery.io/framework-specific-guidance/cypress.md) - [Updating Cypress Tests to Output in JUnit XML Format](https://docs.testery.io/framework-specific-guidance/cypress/updating-cypress-tests-to-output-in-junit-xml-format.md): In this article, we'll walk through the steps to update your Cypress tests to output in JUnit XML format and how to upload them to Testery for automated analysis. - [Playwright](https://docs.testery.io/framework-specific-guidance/playwright.md): Instructions for getting your Playwright tests to run on Testery - [Update Playwright Tests to Output in JUnit XML Format for Import Into Testery](https://docs.testery.io/framework-specific-guidance/playwright/update-playwright-tests-to-output-in-junit-xml-format-for-import-into-testery.md): In this article, we'll guide you through the process of updating your Playwright tests to output results in JUnit XML format, allowing you to seamlessly integrate them into your CI/CD pipeline. Prere - [PyTest](https://docs.testery.io/framework-specific-guidance/pytest.md) - [Update Pytest to Generate JUnit XML for Import into Testery](https://docs.testery.io/framework-specific-guidance/pytest/update-pytest-to-generate-junit-xml-for-import-into-testery.md) - [TestNG](https://docs.testery.io/framework-specific-guidance/testng.md) - [Updating TestNG Tests to Output in JUnit XML Format](https://docs.testery.io/framework-specific-guidance/testng/updating-testng-tests-to-output-in-junit-xml-format.md): In this article, we'll guide you through the process of updating your TestNG tests to output results in JUnit XML format and then uploading these results to Testery for further analysis and monitoring - [Enable or Disable Automatic Rerunning of Tests](https://docs.testery.io/how-to/enable-or-disable-automatic-rerunning-of-tests.md) - [Run Cypress Tests without Connecting Repository](https://docs.testery.io/how-to/run-cypress-tests-without-connecting-repository.md): A step-by-step guide to running Cypress tests on the Testery platform when integration with GitHub / Bitbucket isn't an option. - [How to Store Sensitive Data Like Username and Password For a Cypress Test](https://docs.testery.io/how-to/how-to-store-sensitive-data-like-username-and-password-in-a-cypress-test.md) - [Connect to a Private npm Repository](https://docs.testery.io/how-to/connect-to-a-private-npm-repository.md) - [Running Scripts Before the Tests](https://docs.testery.io/how-to/running-scripts-before-the-tests.md) - [Upload Test Run for Analysis](https://docs.testery.io/how-to/upload-test-run-for-analysis.md) - [Troubleshooting Steps](https://docs.testery.io/misc/troubleshooting-steps.md) - [Fix Common Selenium Exceptions](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions.md) - [Fix a ChromeDriver Version Exception](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions/fix-a-chromedriver-version-exception.md) - [Fix a NoSuchElement Exception](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions/fix-a-nosuchelement-exception.md) - [Fix a TimeoutException](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions/fix-a-timeoutexception.md) - [Fix an ElementNotVisibleException](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions/fix-an-elementnotvisibleexception.md) - [Fix a StaleElementReferenceException](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions/fix-a-staleelementreferenceexception.md) - [Fix a WebDriverException](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions/fix-a-webdriverexception.md) - [Fix an InvalidArgumentException](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions/fix-an-invalidargumentexception.md) - [Fix a NoSuchWindowException](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions/fix-a-nosuchwindowexception.md) - [Fix an UnhandledAlertException](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions/fix-an-unhandledalertexception.md) - [Fix an InvalidSelectorException](https://docs.testery.io/fixing-tests/fix-common-selenium-exceptions/fix-an-invalidselectorexception.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on a page URL with the `ask` query parameter: ``` GET https://docs.testery.io/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.