Skip to content

Add Playwright config to scope test discovery to e2e directory#22

Merged
raymondoyondi merged 1 commit into
mainfrom
agent/swift-noble-aven
Jul 12, 2026
Merged

Add Playwright config to scope test discovery to e2e directory#22
raymondoyondi merged 1 commit into
mainfrom
agent/swift-noble-aven

Conversation

@raymondoyondi

Copy link
Copy Markdown
Owner

Prevents Playwright from collecting vitest unit tests (src/**/*.test.ts) as Playwright tests, which caused 'Vitest failed to access its internal state' errors and exit code 1 during npx playwright test.

Prevents Playwright from collecting vitest unit tests (src/**/*.test.ts)
as Playwright tests, which caused 'Vitest failed to access its internal
state' errors and exit code 1 during npx playwright test.
@raymondoyondi raymondoyondi merged commit db2cd86 into main Jul 12, 2026
4 checks passed
@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@raymondoyondi, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 15 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a84ccc73-0c22-4b86-9008-cfa7bff990a6

📥 Commits

Reviewing files that changed from the base of the PR and between 7a18619 and b7f7a09.

📒 Files selected for processing (1)
  • playwright.config.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch agent/swift-noble-aven

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

Comment @coderabbitai help to get the list of available commands.

@raymondoyondi raymondoyondi deleted the agent/swift-noble-aven branch July 12, 2026 20:36

@gemini-code-assist gemini-code-assist Bot 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.

Code Review

This pull request introduces a new Playwright configuration file (playwright.config.ts) to set up end-to-end testing. The reviewer suggested adding a webServer configuration to automatically spin up the development server before running tests, which would improve the developer experience and prevent test execution failures.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread playwright.config.ts
Comment on lines +10 to +13
use: {
baseURL: 'http://127.0.0.1:3000',
trace: 'on-first-retry',
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

To improve the developer experience and prevent test execution failures when the server is not already running, consider adding a webServer configuration. This allows Playwright to automatically spin up the Vite development server and wait for it to be ready before running any tests.

  use: {
    baseURL: 'http://127.0.0.1:3000',
    trace: 'on-first-retry',
  },
  webServer: {
    command: 'npm run dev',
    url: 'http://127.0.0.1:3000',
    reuseExistingServer: !process.env.CI,
  },

@greptile-apps

greptile-apps Bot commented Jul 12, 2026

Copy link
Copy Markdown

Greptile Summary

This PR adds a Playwright config for E2E test discovery.

  • Adds a root playwright.config.ts.
  • Limits Playwright tests to the ./e2e directory.
  • Sets Chromium-only execution, CI retries, HTML reporting, and trace collection on retry.

Confidence Score: 5/5

This looks safe to merge.

  • No blocking issues found in the changed code.

Important Files Changed

Filename Overview
playwright.config.ts Adds Playwright discovery and runtime defaults that match the current E2E directory and CI setup.

Reviews (1): Last reviewed commit: "Add Playwright config to scope test disc..." | Re-trigger Greptile

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant