fix(test): preserve onboarding runtime fixture isolation - #8558
fix(test): preserve onboarding runtime fixture isolation#8558apurvvkumaria wants to merge 2 commits into
Conversation
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Maintainer security reviewVerdict: PASS — no findings or warnings.
Validation: all eight fixture-consuming suites pass in normal and shuffled order, 64/64 each; diff-scoped repository checks, CLI type checking, normal push gates, and secret scanning pass. Scope is seven test-only files with no production, dependency, workflow, policy, or documentation changes. |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall coverage in commit 7c4e077 in the TypeScript / code-coverage/cliThe overall coverage in commit 7c4e077 in the Show a code coverage summary of the most impacted files.
Updated |
|
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 (7)
💤 Files with no reviewable changes (5)
📝 WalkthroughWalkthroughChangesOnboarding session cloning
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
PR Review Advisor — No blocking findings reportedAdvisor assessment: No blocking advisor findings reported Model lanes
Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests. E2E guidanceAdvisory only. A maintainer can dispatch the default E2E suite against this exact revision. Recommended E2E: This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge. |
|
Closing as superseded by #8557, merged in |
Summary
PR #8546 introduced a shared onboarding runtime fixture whose normalization fallback could return the caller-owned session, allowing later test mutation to leak into earlier state. This follow-up always returns the serialized copy, adds a regression for the isolation contract, and removes imports left unused by the migration.
Related Issue
Refs #8289. Follow-up to #8546 and its unresolved review finding.
Changes
cloneSessionreturn its serialized copy whennormalizeSessionrejects test data, preserving the fixture's independent-state contract.Type of Change
Quality Gates
Documentation Writer Review
no-docs-neededDGX Station Hardware Evidence
Verification
Signed-off-by:line and every commit appears asVerifiedin GitHubpre-commit,commit-msg, andpre-pushhooks passed, ornpm run validate:prpassed after refreshingorigin/mainwhen hooks were skipped or unavailable — normal commit and pre-push gates passed; a full diff-scoped hook fallback also passed.npm testfor broad runtime/test-harness changes;npm run checkfor repo-wide validation/coverage changes — command/result: not applicable. This adjusts one test-helper fallback without changing Vitest configuration, setup, project registration, production code, or runtime behavior; all eight helper consumers were exercised directly.npm run docsbuilds without warnings (doc changes only)Signed-off-by: Apurv Kumaria akumaria@nvidia.com
Summary by CodeRabbit
Bug Fixes
Tests