Node.js Test Runner Meeting 2026-08-26

Open
#41 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Tech stack
node.js
Domain
testing

Research direction

This is a meeting announcement rather than a change request, and it names no source files or tests. Start with the linked minutes and the listed agenda issues (#64171, #61854, #21, and #13) if context is needed. No implementation scope or completion condition is defined beyond the meeting details.

Written by the indexing model from the issue text.

Description

Time

UTC Wed, Aug 26, 2026, 07:30 PM:

Timezone Date/Time
US / Pacific Wed, Aug 26, 2026, 12:30 PM
US / Mountain Wed, Aug 26, 2026, 01:30 PM
US / Central Wed, Aug 26, 2026, 02:30 PM
US / Eastern Wed, Aug 26, 2026, 03:30 PM
EU / Western Wed, Aug 26, 2026, 08:30 PM
EU / Central Wed, Aug 26, 2026, 09:30 PM
EU / Eastern Wed, Aug 26, 2026, 10:30 PM
Moscow Wed, Aug 26, 2026, 10:30 PM
Chennai Thu, Aug 27, 2026, 01:00 AM
Hangzhou Thu, Aug 27, 2026, 03:30 AM
Tokyo Thu, Aug 27, 2026, 04:30 AM
Sydney Thu, Aug 27, 2026, 05:30 AM

Or in your local time:

Links

Invited

  • @nodejs/test_runner
Observers/Guests

None.

Agenda

Issues and Pull Requests

Extracted from test_runner-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node
  • test_runner: exclude files with no matching tests from report #64171
  • Unexpected behaviour of beforeEach outside of suite without test isolation #61854
nodejs/test-runner
  • High Impact Suggestions for the Team #21
  • doc(proposal): un/break --test #13

Joining the meeting


Invitees

Please use the following emoji reactions in this post to indicate your availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure
Dominant language
No language data
Stars
3
Forks
4
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/test-runner

All issues in nodejs/test-runner

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.