Fix TypeScript matcher typing issue
CI Pipeline / test (pull_request) Successful in 7m5s
CI Pipeline / lint (pull_request) Has been cancelled
CI Pipeline / build (pull_request) Has been cancelled
CI Pipeline / e2e (webkit) (pull_request) Has been cancelled
CI Pipeline / e2e (chromium) (pull_request) Successful in 54m11s
CI Pipeline / e2e (firefox) (pull_request) Failing after 22m9s
CI Pipeline / visual-regression (pull_request) Successful in 11m50s
CI Pipeline / performance (pull_request) Successful in 13m59s

This commit is contained in:
adilallo
2026-01-28 15:57:47 -07:00
parent 2652015e80
commit 9cb89162ab
28 changed files with 69 additions and 90 deletions
+3 -2
View File
@@ -74,7 +74,9 @@ const config: ComponentTestSuiteConfig<Props> = {
error: {
props: { error: true } as Partial<Props>,
assert: (el) => {
expect(el).toHaveClass("border-[var(--color-border-default-utility-negative)]");
expect(el).toHaveClass(
"border-[var(--color-border-default-utility-negative)]",
);
},
},
},
@@ -214,4 +216,3 @@ Accessibility is tested at two levels:
- Tests complete user journeys for accessibility barriers
This two-tier approach ensures both individual components and full page experiences meet accessibility standards.