Repository navigation
fix: adding mock server to test - #9503
utkarsh-bruno wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review. WalkthroughThe default ChangesEnd-to-end project selection
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~8 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The standard end-to-end command now includes the configured mock-server project, with no concrete issue identified that blocks merging. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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. Three projects join the test command Comment |
Description
Mock Server end-to-end tests were left out of the suite CI actually runs. npm run test:e2e now includes the mock-server Playwright project, and the testing notes match that.
Problem
npm run test:e2e only ran the default and system-pac projects. CI uses that script, so the Mock Server suite never ran there. auth and ssl stay on their own jobs.
Fix
Add --project=mock-server to the test:e2e script. The default Playwright ignore is unchanged, so the suite is not collected twice when both default and mock-server are selected.
Contribution Checklist:
Summary by CodeRabbit