docs(e2e): sync full-e2e budget note#6762
Conversation
Signed-off-by: HwangJohn <angelic805@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe E2E README updates the ChangesE2E Performance Budget
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
E2E Advisor RecommendationRequired E2E: None Full advisor summaryE2E Recommendation AdvisorBase: Required E2E
Optional E2E
New E2E recommendations
|
|
✨ Thanks for the docs sync, @HwangJohn. Updating the README budget to match the current 205-second total keeps the test harness documentation accurate. Ready for maintainer review. Related open issues: |
Summary
Sync the
full-e2eREADME budget prose with the current hard total budget. The live full-E2E test uses a 205-second total budget, but the README still described the old 180-second limit.Related Issue
Refs #6660.
Changes
test/e2e/README.mdonboard performance budget section from180 secondsto205 seconds.Type of Change
Quality Gates
docs/.Verification
Verifiedin GitHubpre-commit,commit-msg, andpre-pushhook-equivalent checks passedrg -n "ONBOARD_BUDGET_SECS|180 seconds|205 seconds" test/e2e/README.md test/e2e/live/full-e2e.test.tsconfirms the README now matches the 205-second budget source.npm testfor broad runtime/test-harness changes;npm run checkfor repo-wide validation/coverage changes — command/result:npm run docsbuilds without warnings (doc changes only)Signed-off-by: HwangJohn angelic805@gmail.com
Summary by CodeRabbit