Skipped flaky welcome emails test#27499
Conversation
WalkthroughA Playwright test case in the admin member welcome emails test file is modified to be skipped during test execution. Specifically, the test named "Escape closes welcome email color picker without bypassing unsaved changes confirmation" is converted from an active test to a skipped test by changing the test invocation from 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
e2e/tests/admin/settings/member-welcome-emails.test.ts (1)
272-272: Add a tracking reference next to the skip.The skip has no inline pointer to the Linear issue (NY-1234), which makes it easy to forget. Consider adding a short comment above the
test.skip(...)so anyone touching this file later knows why it's skipped and where to track re-enablement.Proposed change
+ // Skipped due to flakiness — see NY-1234 test.skip('Escape closes welcome email color picker without bypassing unsaved changes confirmation', async ({page}) => {🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@e2e/tests/admin/settings/member-welcome-emails.test.ts` at line 272, Add an inline tracking reference comment immediately above the test.skip call for the test named 'Escape closes welcome email color picker without bypassing unsaved changes confirmation' so future editors know why it's skipped and where to track re-enablement (e.g., "TODO: skipped due to NY-1234 - re-enable when ..."). Update the comment to include the Linear issue ID (NY-1234) and a brief one-line reason or owner; leave the test.skip(...) call unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@e2e/tests/admin/settings/member-welcome-emails.test.ts`:
- Line 272: Add an inline tracking reference comment immediately above the
test.skip call for the test named 'Escape closes welcome email color picker
without bypassing unsaved changes confirmation' so future editors know why it's
skipped and where to track re-enablement (e.g., "TODO: skipped due to NY-1234 -
re-enable when ..."). Update the comment to include the Linear issue ID
(NY-1234) and a brief one-line reason or owner; leave the test.skip(...) call
unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 7abb6123-0826-4e19-b740-296fd5e4a03c
📒 Files selected for processing (1)
e2e/tests/admin/settings/member-welcome-emails.test.ts
|



ref https://linear.app/ghost/issue/NY-1234/flaky-member-welcome-emails-e2e-test
This test has been flaky recently. Skipping it for now to avoid disrupting CI while I work on a fix.