Node.js 18.7 Adds Built-in Test Runner

Node.js 18.7.0 landed on 7 July 2022 with an experimental built-in test runner and stabilized fetch for global HTTP requests. The release gives teams an officially supported test capability without relying on third-party frameworks and paves the way for more consistent HTTP client behavior across runtimes.

What is new

• The built-in test runner (node --test) entered experimental status, supporting subtests, hooks, and TAP output.
• The global fetch API moved toward stabilization, aligning Node.js with web platform standards.
• Other improvements included diagnostics channel updates and performance refinements in the V8 JavaScript engine.

Why it matters

• Teams can reduce dependency sprawl by consolidating on the core test runner for lightweight suites while retaining Jest or Mocha for advanced features.
• CI pipelines may see faster startup and reduced maintenance with built-in tooling, but need validation for reporters and coverage integrations.
• HTTP client behavior now aligns more closely with browser fetch semantics, easing code sharing between frontend and backend.

Adoption guidance

• Enable the experimental test runner in a staging branch and benchmark execution time and reporter compatibility.
• Update linting and coding standards to reflect the availability of fetch and to avoid mixing legacy node-fetch behaviors.
• Monitor Node.js release notes for graduation of the test runner from experimental status and incorporate in LTS upgrade planning.

Recommended practices

Development teams should adopt practices that ensure code quality and maintainability during and after this transition:

• Code review focus areas: Update code review checklists to include checks for deprecated patterns, new API usage, and migration-specific concerns. Establish review guidelines for changes that span multiple components.
• Documentation updates: Ensure README files, API documentation, and architectural decision records reflect the changes. Document rationale for setup choices to aid future maintenance.
• Version control practices: Use feature branches and semantic versioning to manage the transition. Tag releases clearly and maintain changelogs that highlight breaking changes and migration steps.
• Dependency management: Lock dependency versions during migration to ensure reproducible builds. Update package managers and lockfiles systematically to avoid version conflicts.
• Technical debt tracking: Document any temporary workarounds or deferred improvements introduced during migration. Create backlog items for post-migration cleanup and improvement.

Consistent application of development practices reduces risk and accelerates delivery of reliable software.

Ongoing maintenance

If you are affected, plan for ongoing maintenance and evolution of systems affected by this change:

• Support lifecycle awareness: Track support timelines for dependencies, runtimes, and platforms. Plan upgrades before end-of-life dates to maintain security patch coverage.
• Continuous improvement: Establish feedback loops to identify improvement opportunities. Monitor performance metrics and user feedback to guide iterative improvements.
• Knowledge management: Build team expertise through training, documentation, and knowledge sharing. Ensure institutional knowledge is preserved as team composition changes.
• Upgrade pathways: Maintain awareness of future versions and breaking changes. Plan incremental upgrades rather than large leap migrations where possible.
• Community engagement: Participate in relevant open source communities, user groups, or vendor programs. Stay informed about roadmaps, good practices, and common pitfalls.

preventive maintenance planning reduces technical debt accumulation and ensures systems remain secure, performant, and aligned with business needs.

• Test coverage analysis: Review existing test suites to identify gaps in coverage for affected functionality. Prioritize test creation for high-risk areas and critical user journeys.
• Regression testing: Establish full regression test suites to catch unintended side effects. Automate regression runs in CI/CD pipelines to catch issues early.
• Performance testing: Conduct load and stress testing to validate system behavior under production-like conditions. Establish performance baselines and monitor for degradation.
• Security testing: Include security-focused testing such as SAST, DAST, and dependency scanning. Address identified vulnerabilities before production deployment.
• User acceptance testing: Engage teams in UAT to validate that changes meet business requirements. Document acceptance criteria and sign-off procedures.

A full testing strategy provides confidence in changes and reduces the risk of production incidents.

Cross-team coordination

Effective collaboration across teams ensures successful adoption and ongoing support:

• Cross-functional alignment: Coordinate with product, design, QA, and operations teams on setup timelines and dependencies. Establish regular sync meetings during transition periods.
• Communication channels: Create dedicated channels for questions, updates, and issue reporting related to this change. Ensure relevant teams are included in communications.
• Knowledge sharing: Document lessons learned and share good practices across teams. Conduct tech talks or workshops to build collective understanding.
• Escalation paths: Define clear escalation procedures for blocking issues. Ensure decision-makers are identified and available during critical phases.
• Retrospectives: Schedule post-setup retrospectives to capture insights and improve future transitions. Track action items and follow through on improvements.

Strong collaboration practices accelerate delivery and improve outcomes across the organization.

• Risk identification: Catalog potential risks including technical failures, timeline delays, resource constraints, and external dependencies. Assess likelihood and impact for each risk.
• Mitigation strategies: Develop mitigation plans for high-priority risks. Assign ownership and track mitigation progress through regular reviews.
• Contingency planning: Prepare fallback options and recovery procedures for critical risks. Test contingency plans to ensure they are viable when needed.
• Risk monitoring: Establish indicators and triggers for risk escalation. Monitor risk status throughout the setup lifecycle.
• Lessons learned: Document risks that materialized and evaluate mitigation effectiveness. Apply insights to improve risk management for future initiatives.

early risk management reduces surprises and enables more predictable delivery outcomes.

You may also find useful

Hand-picked articles on adjacent topics.

Developer · Credibility 73/100 · April 19, 2022

Node.js 18 and Modern Runtime Features

Node.js 18 debuted on April 19 2022 as the project’s ‘Current’ release line. Also to an update to V8 10.1 and planned promotion to long‑term support (LTS) status in October 2022 with the codename Hydrogen (supported…

Developer · Credibility 40/100 · January 26, 2023

Rust 1.67 Release

Rust 1.67 release in January 2023 continued the language's evolution. Async improvements and standard library additions. Rust's growth in systems programming and security-sensitive applications continued.

Developer · Credibility 90/100 · September 14, 2021

Java 17 long-term support release

Java 17 LTS dropped on September 14, 2021—the first long-term support release since Java 11. Sealed classes, pattern matching improvements, and better crypto defaults. Support runs through 2029.

Developer · Credibility 91/100 · October 2, 2023

Python 3.12 General Availability

Python 3.12 shipped with better error messages, per-interpreter GIL for subinterpreters, and the new 'type' statement for type aliases. Performance is up 5% across the board.

Developer · Credibility 40/100 · June 21, 2022

Developer Productivity — GitHub Copilot General Availability

GitHub Copilot is no longer invite-only. As of June 21, 2022, any developer can subscribe and start using AI-assisted code completion in their IDE. This is the first major commercial AI coding assistant, and it is going…

Continue in the Developer pillar

Return to the hub for curated research and deep-dive guides.

Visit pillar hub

Latest guides

• Secure Software Supply Chain Tooling Guide

  Engineer developer platforms that deliver verifiable provenance, SBOM distribution, vendor assurance, and runtime integrity aligned with SLSA v1.0, NIST SP 800-204D, and CISA SBOM…

• AI-Assisted Development Governance Guide

  Govern GitHub Copilot, Azure AI, and internal generative assistants with controls aligned to NIST AI RMF 1.0, EU AI Act enforcement timelines, OMB M-24-10, and enterprise privacy…

• Developer Enablement & Platform Operations Guide

  Plan AI-assisted development, secure SDLC controls, and runtime upgrades using our research on GitHub Copilot, GitHub Advanced Security, and major language lifecycles.

Coverage intelligence

Published

July 7, 2022

Coverage pillar

Developer

Source credibility

40/100 — low confidence

Topics

Node.js · Testing · Runtimes · Developer Productivity · JavaScript

Sources cited

3 sources (nodejs.org, iso.org)

Reading time

5 min

Documentation

1. Node.js 18.7.0 release notes
2. Node.js test runner documentation
3. ISO/IEC 27034-1:2011 — Application Security — International Organization for Standardization