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
  • Switching to Python 3.9 before October 31, 2024
  • Defaulting to new version without a testery.yml

Was this helpful?

  1. Get to Know Testery
  2. Test Stacks

Python 3.8 End of Life

PreviousDefault Chrome Version ChangeNextDeployments

Last updated 6 months ago

Was this helpful?

Handling the Upgrade to new python

On October 7th, 2024 python 3.8 reached its end of life date. For details, see

On October 31st, 2024 at 12pm Central Time, Testery decommission test stack images running with python 3.8

We encourage all Testery customers to migrate before this date, however, we will maintain Python 3.8 support until October 31, 2024

Switching to Python 3.9 before October 31, 2024

Migrating your code to the new Test Stack is easy, you just need to provide a testery.yml file in your source repository. Add the following content:

test_stack:
  configuration_key: python-chrome.123-java.17-nodejs.20-python.3.9

Defaulting to new version without a testery.yml

If you choose to not migrate beforehand, the test runs will automatically pick up the new default test stack python-chrome.123-java.17-nodejs.20-python.3.9 after October 31st. This may result in test run failures if you have not checked compatibility beforehand.

https://devguide.python.org/versions/