docs: update testing setupTimeout and add teardownTimeout

[Yizack]

📚 Description

While looking at the @nuxt/test-utils package I noticed setupTimeout default value was updated and teardownTimeout was added in this commit nuxt/test-utils@af2ddf2

This PR updates setupTimeout default value and adds teardownTimeout

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[coderabbitai]

Walkthrough

The documentation for end-to-end testing has been updated to reflect changes in the default timeout values for the setupTimeout option, increasing it from 60,000 ms to 120,000 ms, and to 240,000 ms specifically on Windows platforms. Additionally, a new teardownTimeout option has been documented, allowing configuration of the timeout for tearing down the test environment, with a default of 30,000 ms. Both options are described with their types and default values.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/1.getting-started/17.testing.md (1)

607-608: Capitalise “Windows” for consistency and correctness

“windows” is a proper noun referring to the Microsoft OS and should be capitalised.

-  - Default: `120000` or `240000` on windows
+  - Default: `120000` or `240000` on Windows

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bfd30d8 and 63abb97.

📒 Files selected for processing (1)

• docs/1.getting-started/17.testing.md (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: applies to **/e2e/**/*.{ts,js} : write end-to-end tests using playwright and `@nuxt/test-utils`...

Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/e2e/**/*.{ts,js} : Write end-to-end tests using Playwright and `@nuxt/test-utils`

Applied to files:

• docs/1.getting-started/17.testing.md

📚 Learning: applies to **/*.{test,spec}.{ts,tsx,js,jsx} : write unit tests for core functionality using `vitest`...

Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/*.{test,spec}.{ts,tsx,js,jsx} : Write unit tests for core functionality using `vitest`

Applied to files:

• docs/1.getting-started/17.testing.md

🪛 LanguageTool

docs/1.getting-started/17.testing.md

[grammar] ~607-~607: “Windows” (operating system by Microsoft) is a proper noun and needs to be capitalized.
Context: ...r - Default:120000or240000on windows -teardownTimeout`: The amount of tim...

(A_WINDOWS)

---

[uncategorized] ~609-~609: Loose punctuation mark.
Context: ...240000 on windows - teardownTimeout: The amount of time (in milliseconds) to...

(UNLIKELY_OPENING_PUNCTUATION)

🔇 Additional comments (1)

docs/1.getting-started/17.testing.md (1)

609-611: teardownTimeout entry reads well – no further changes needed

The description, type annotation, and default value align with the existing documentation style.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/1.getting-started/17.testing.md (1)

607-607: Capitalise “Windows” and tighten wording

“Windows” is a proper noun and should be capitalised. Placing the alternative default in parentheses also reads better.

-  - Default: `120000` or `240000` on windows
+  - Default: `120000` (or `240000` on Windows)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 63abb97 and 8001a97.

📒 Files selected for processing (1)

• docs/1.getting-started/17.testing.md (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: applies to **/e2e/**/*.{ts,js} : write end-to-end tests using playwright and `@nuxt/test-utils`...

Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/e2e/**/*.{ts,js} : Write end-to-end tests using Playwright and `@nuxt/test-utils`

Applied to files:

• docs/1.getting-started/17.testing.md

📚 Learning: applies to **/*.{test,spec}.{ts,tsx,js,jsx} : write unit tests for core functionality using `vitest`...

Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/*.{test,spec}.{ts,tsx,js,jsx} : Write unit tests for core functionality using `vitest`

Applied to files:

• docs/1.getting-started/17.testing.md

🪛 LanguageTool

docs/1.getting-started/17.testing.md

[grammar] ~607-~607: “Windows” (operating system by Microsoft) is a proper noun and needs to be capitalized.
Context: ...r - Default:120000or240000on windows -teardownTimeout`: The amount of tim...

(A_WINDOWS)

---

[uncategorized] ~609-~609: Loose punctuation mark.
Context: ...240000 on windows - teardownTimeout: The amount of time (in milliseconds) to...

(UNLIKELY_OPENING_PUNCTUATION)

🔇 Additional comments (1)

docs/1.getting-started/17.testing.md (1)

609-611: teardownTimeout docs look good

The new option’s description, type, and default match the upstream implementation. No changes needed.