# Node.js 24.20 adds test-runner logging to its LTS line

> Node.js 24.20 expands test-runner events with contextual logging and entry-file information, alongside additions to asynchronous context and streams.

Canonical URL: https://www.devobs.io/news/news-node-2420-test-reporting/
By: Maya Chen
Published: 2026-09-06T11:58:54.644Z
Updated: 2026-09-06T11:58:54.644Z
Event date: 2026-08-26
Section: Languages

Node.js released version 24.20.0 on August 26 for its Krypton LTS line. The [release notes](https://nodejs.org/en/blog/release/v24.20.0) include test-runner additions that give custom reporting tools more context about what happened during a run.

## Test events carry more context

The update adds `context.log()`, a corresponding test-log event, and an entry-file field in test-stream events. Other listed additions include using scopes for `AsyncLocalStorage` and a new stream-iterator implementation.

For teams with a custom reporter, contextual logs suggest an opportunity to connect diagnostic output to the test that produced it. The value is clearest in a concurrent suite, where a flat stream of messages can force engineers to reconstruct which operation failed.

## Verify the reporter, not just the test

A reporter evaluation should include overlapping tests, a test that fails after logging, and a test that terminates before its usual cleanup. Inspect the machine-readable result as well as the console rendering. A helpful local display can still lose the relationship between a message and its test when exported to a CI system.

Keep retained logs purposeful. Decide which diagnostic fields are needed to reproduce a failure, how long results remain available, and whether application data enters those fields. Better event structure is an opportunity to make diagnostics more selective, rather than simply increase their volume.

Because the additions land on an LTS line, teams can assess the reporting changes within their existing major-version strategy. The concrete success criterion is faster identification of a failed test's relevant evidence, with the same trustworthy pass and failure accounting as before.

## Source references

- <https://nodejs.org/en/blog/release/v24.20.0>
