Repository navigation
Conversation
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>
|
Review requested:
|
|
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. |
|
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 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. |
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