Node.js Test Runner Meeting 2026-07-29

Open
#39 0 comments 2 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

Research direction

This issue is a scheduled Node.js Test Runner meeting notice, not an implementation task. Read the agenda and linked minutes to understand the meeting context; there are no files or tests named, and completion is limited to the meeting and availability responses.

Written by the indexing model from the issue text.

Description

Time

UTC Wed, Jul 29, 2026, 07:30 PM:

Timezone Date/Time
US / Pacific Wed, Jul 29, 2026, 12:30 PM
US / Mountain Wed, Jul 29, 2026, 01:30 PM
US / Central Wed, Jul 29, 2026, 02:30 PM
US / Eastern Wed, Jul 29, 2026, 03:30 PM
EU / Western Wed, Jul 29, 2026, 08:30 PM
EU / Central Wed, Jul 29, 2026, 09:30 PM
EU / Eastern Wed, Jul 29, 2026, 10:30 PM
Moscow Wed, Jul 29, 2026, 10:30 PM
Chennai Thu, Jul 30, 2026, 01:00 AM
Hangzhou Thu, Jul 30, 2026, 03:30 AM
Tokyo Thu, Jul 30, 2026, 04:30 AM
Sydney Thu, Jul 30, 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
  • test-runner: requireing a mocked dual-package gets the original instead of the mock #58231
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 Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.