test(inspector): expand granular Node parity coverage#6490
Conversation
|
Warning Review limit reached
Next review available in: 15 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe PR adds a deterministic ChangesInspector parity suite
Estimated code review effort: 4 (Complex) | ~60 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ 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 |
…ector-parity # Conflicts: # test-parity/node_suite_baseline.json
Summary
node:inspectorcallback parity suite from 3 to 37 entriespost()validation and callback behavior, deterministic Runtime/Schema/Debugger/Profiler/HeapProfiler commands, notifications, and isolated endpoint semanticsnode:inspector/promisesfollow-on boundaryValidation
fedccaf62d97bd5c1ebe1589a063e872222510b591536816ab38fe5bfb39fecdcargo build --release -p perry -p perry-runtime-static -p perry-stdlib-static --locked --offlinecargo fmt --all -- --checkdeno fmt --check test-parity/node-suite/inspector test-parity/node_suite_baseline.jsonExclusions
CPU/heap sampling, coverage payloads, snapshots, GC/finalization, breakpoints, active
waitForDebugger, signals, stress, external frontends/clients, and scheduler-sensitive worker behavior remain excluded.node:inspector/promisesremains the correct separate next suite.Summary by CodeRabbit
New Features
node:inspectorparity coverage across events, sessions, lifecycle behavior, protocol commands, runtime evaluation, network helpers, and API surface details.Documentation