test(solid-query-devtools/devtoolsPanel): use 'toHaveStyle' matcher in the 'style' merge cases#10846
Conversation
…n the 'style' merge cases
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughTest assertions in the devtools panel test file were refactored to validate ChangesContainer styling test assertions
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit 9c93f75
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version Preview2 package(s) bumped directly, 23 bumped as dependents. 🟩 Patch bumps
|
size-limit report 📦
|
🎯 Changes
Replace the manual
as HTMLElementcasts and.style.height/.style.widthchecks in the twostylemerge test cases with thetoHaveStylematcher from@testing-library/jest-dom.This is now possible thanks to #10845, which added
test-setup.tsto the tsconfigincludeso jest-dom matcher type augmentations are picked up.Before:
After:
Benefits:
as HTMLElementcast — the matcher acceptsElement | nulldirectlyexpectreads the assertion as one logical steptoHaveStylereports a clear failure when the element is missing✅ Checklist
🚀 Release Impact
Summary by CodeRabbit