Wait for a toast to disappear before comparing snapshots in taking-exam#1662
Wait for a toast to disappear before comparing snapshots in taking-exam#1662
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (4)
📝 WalkthroughWalkthroughIntroduces explicit synchronization and stability waits in system tests: wraps several action sequences with Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 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.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@system-tests/src/tests/exams/taking-exam.spec.ts`:
- Around line 29-32: The current wait on
page.getByTestId("toast-notification").waitFor(...).catch(() => {}) swallows
failures and hides flakiness; replace this with the project's success-toast sync
pattern by calling the shared helper waitForSuccessNotification (or, if
unavailable, remove the .catch so the wait can fail) after the start-exam
mutation. Locate the usage of page.getByTestId("toast-notification")/waitFor in
taking-exam.spec.ts and swap it for waitForSuccessNotification(...) or let the
wait throw so the test fails when the toast does not appear.
Summary by CodeRabbit