Skip to content

doc: introduce suites section in test runner documentation - #67471

Open
hazalkoom wants to merge 1 commit into
nodejs:mainfrom
hazalkoom:doc-60758-test-runner-suites
Open

hazalkoom wants to merge 1 commit into
nodejs:mainfrom
hazalkoom:doc-60758-test-runner-suites

Conversation

@hazalkoom

Copy link
Copy Markdown

Introduce a concise Suites section before Subtests in doc/api/test.md to explain how suite() groups tests and automatically waits for nested tests and suites to complete.

Fixes: #60758

Assisted-by: Antigravity antigravity@google.com

Introduce a concise Suites section before Subtests in doc/api/test.md
to explain how suite() groups tests and automatically waits for nested
tests and suites to complete.

Fixes: nodejs#60758
Signed-off-by: Mohamed Ahmed <mwhamd345@gmail.com>
Assisted-by: Antigravity <antigravity@google.com>
Copilot AI balanced review requested due to automatic review settings November 14, 2026 19:09
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/test_runner

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to Node.js documentation. test_runner Issues and PRs related to the test runner subsystem. labels Nov 14, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Welcome to Node.js, and thank you for your first contribution!

Before review, please take a moment to read:

Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal.

@MikeMcC399

Copy link
Copy Markdown
Member

The recommendations in:

advise you should tackle only one issue at a time and that you should not open any new PRs until your first PR has been approved.

You already have another unapproved PR #67405 open at this time.

Until the first PR has been approved and has landed in the main branch, GitHub classifies you as "first-time contributor". Each PR commit you push needs to be individually approved by team members to run in GitHub Actions CI. This causes delays for you as a contributor, and it adds to the work load for the team.

Waiting until the first PR has landed ensures that you as a contributor have experienced the complete process from PR submission to successful landing. After this has been completed, any new PRs or new commits to an existing PR are treated to rules for regular Contributors. GitHub Actions CI workflows are then run automatically without intervention by a team member.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to Node.js documentation. test_runner Issues and PRs related to the test runner subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Test Runner docs could use more information on the concept of a Suite

4 participants