Bulk import plugin: Add missing assertion (expect) to runAccessibilityTests

[christoph-jerolimov]

The bulk import plugins has playwright tests that include a bunch of accessibility assertions.

The tests runs runAccessibilityTests from @workspaces/bulk-import/e2e-tests/utils/helpers.ts, but the accessibilityScanResults.violations isn't used in any assertion.

Add expect(accessibilityScanResults.violations, 'Accessibility violations found').toEqual([]); to that function.

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 1:56 PM UTC · Completed 1:58 PM UTC
Commit: 381f36a · View workflow run →

[fullsend-ai-triage]

Triage Summary

This is a well-defined bug fix request. The runAccessibilityTests helper in @workspaces/bulk-import/e2e-tests/utils/helpers.ts collects accessibility violations but never asserts on them, meaning the tests silently pass regardless of any accessibility issues.

Severity: Low — no user-facing impact, but the test gap means accessibility regressions could go undetected.

Recommended fix: Add the missing assertion to the helper function:

expect(accessibilityScanResults.violations, 'Accessibility violations found').toEqual([]);

After adding the assertion, run the existing e2e tests to confirm they still pass. If the assertion surfaces new violations, those should be fixed as part of or immediately following this change.

Proposed test verification:

1. Run existing bulk-import Playwright e2e tests — they should pass with the assertion added.
2. To verify the assertion is effective, temporarily inject a known a11y violation
   (e.g., remove an aria-label from a UI element) and confirm the test now fails
   with a clear violation message.

This looks like a good first issue — the scope is narrow and the fix is clearly described.

---

Labels: Adding Tests label since this issue is specifically about fixing test assertions in the e2e test suite.

Previous run

Triage Summary

This is a well-defined bug fix request. The runAccessibilityTests helper in the bulk-import plugin's e2e tests collects accessibility violations but never asserts on them, meaning the tests silently pass regardless of any accessibility issues.

Severity: Low — no user-facing impact, but the test gap means accessibility regressions could go undetected.

Recommended fix: Add the missing assertion to @workspaces/bulk-import/e2e-tests/utils/helpers.ts:

expect(filteredViolations, 'Accessibility violations found').toEqual([]);

After adding the assertion, run the existing e2e tests to confirm they still pass. If the assertion surfaces new violations, those should be fixed as part of or immediately following this change.

Proposed test verification:

1. Run existing bulk-import Playwright e2e tests — they should pass with the assertion added.
2. To verify the assertion is effective, temporarily inject a known a11y violation
   (e.g., remove an aria-label from a UI element) and confirm the test now fails
   with a clear violation message.

This looks like a good first issue — the scope is narrow and the fix is clearly described.

---

Labels: Issue targets the bulk-import workspace with a test fix that is well-suited for newcomers.

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 2:01 PM UTC · Completed 2:14 PM UTC
Commit: 381f36a · View workflow run →

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 7:13 PM UTC · Completed 7:16 PM UTC
Commit: bf40fcb · View workflow run →

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 7:20 PM UTC · Completed 7:22 PM UTC
Commit: bf40fcb · View workflow run →