Skip to content

test: assert notification and account state instead of styling - #3504

Merged
setchy merged 1 commit into
mainfrom
test/assert-state-not-styling
Oct 25, 2026
Merged

setchy merged 1 commit into
mainfrom
test/assert-state-not-styling

Conversation

@setchy

@setchy setchy commented Oct 25, 2026

Copy link
Copy Markdown
Member

Summary

  • Add a data-animating-exit state to notification rows and assert that in the browser suite instead of the opacity-0 utility class.
  • Update the account scopes tests to query the button by its accessible name and assert its data-variant; remove the icon colour-class assertions.

Why

Both assertions were coupled to Tailwind implementation details. The stable state/variant attributes describe the same behaviour without breaking on styling changes. The account tests still verify the correct icon (octicon-shield-check) and the semantic button variant.

Verification

  • pnpm test: 200 files, 1,968 tests passed
  • Notification-list browser tests: 12 passed
  • pnpm exec vp check --no-fmt: 465 files passed

Expose a stable data-animating-exit state on notification rows so visual tests stop reading the opacity utility class. Accounts scope tests now use the button's accessible name and variant, dropping the icon colour-class assertions.
@setchy
setchy requested a review from afonsojramos as a code owner October 25, 2026 13:54
@github-actions github-actions Bot added the test Enhancements to test coverage or quality label Oct 25, 2026
@setchy
setchy merged commit 9eb6ca6 into main Oct 25, 2026
15 checks passed
@setchy
setchy deleted the test/assert-state-not-styling branch October 25, 2026 13:57
@github-actions github-actions Bot added this to the Release 7.11.0 milestone Oct 25, 2026
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test Enhancements to test coverage or quality

Development

Successfully merging this pull request may close these issues.

1 participant