tests(fix): isolate release fixtures from live smoke decisions - #62
Conversation
Summary: - Clear the inherited smoke decision before selecting fixture inputs. Rationale: - Live dispatch exports the waiver into make check. Ordinary release fixtures must still exercise their explicit no-waiver expectations. Tests: - DESKTOP_SMOKE_ATTESTATION=waived-by-maintainer bash test/release/github-test.sh - make lint
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe release test script now clears ChangesRelease test isolation
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to Release fixtures now ignore inherited desktop smoke-waiver state while preserving explicit fixture waivers. No current merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
A live release exports its Desktop smoke decision into
make check. The new waiver consequently reached ordinary GitHub-release fixtures, which correctly rejected their fixture notes as missing disclosure. Clear the inherited decision at the test boundary; individual waiver scenarios still set it explicitly.Validated with
DESKTOP_SMOKE_ATTESTATION=waived-by-maintainer bash test/release/github-test.shandmake lint. The live release stopped in read-only verification and made no tag or publication changes.Summary by CodeRabbit
DESKTOP_SMOKE_ATTESTATIONenvironment setting, ensuring results are controlled by each fixture.