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 Node.js 18 before September 11, 2023
  • Remaining on Node.js 18 after September 11, 2023

Was this helpful?

  1. Get to Know Testery
  2. Test Stacks

Node.js 16 End of Life

Handling the Upgrade to Node 18

PreviousPythonNextDefault Chrome Version Change

Last updated 1 year ago

Was this helpful?

On September 11, 2023, Node.js will reach its end of life date. For details, see

On September 11, 2023 at 12pm Central Time, Testery will begin running all linux Node.js workloads against Node.js 18.

We encourage all Testery customers to migrate before this date, however, we will maintain Node 16 support until September 30, 2023

Switching to Node.js 18 before September 11, 2023

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: node-chrome.114-java.17-nodejs.18

Remaining on Node.js 18 after September 11, 2023

You may use a legacy runner until September 30, 2023 by providing a testery.yml file in your source repository. Add the following content

test_stack:
  configuration_key: node-chrome.114-java.17-nodejs.16
https://nodejs.org/en/blog/announcements/nodejs16-eol