boost: Add E2E test suite with Playwright for AI Catalog browse page

[rohitkrai03]

Problem

Context: RHIDP-15480 tasks 6.1-6.19. The boost workspace has no end-to-end tests. The AI Catalog browse page has unit tests but no integration tests verifying full user flows against a real dev server. Other workspaces (e.g. adoption-insights) have Playwright suites as reference.

Expected behavior

A Playwright E2E test suite covering the browse page core flows:

1. Browse page loads with fixture card grid
2. Search filters cards, URL updates with ?q=
3. Sidebar filter narrows results
4. Multiple filters combine as AND
5. Clear filters restores full grid
6. Card click navigates to entity detail page
7. Empty state on impossible filter combo
8. Pagination controls work
9. axe-core accessibility audit (unfiltered + filtered)

Scope

Workspace: workspaces/boost (workspace root, not inside a plugin package)

New files: playwright.config.ts, e2e-tests/ai-catalog-browse.spec.ts, e2e-tests/utils/translations.ts, e2e-tests/utils/accessibility.ts

Modify: package.json (add test:e2e script, install @playwright/test and @axe-core/playwright)

Implementation details

Playwright config: webServer starts yarn start, testDir e2e-tests, NFS-only (no APP_MODE). Translation helper loads from plugin ref.ts so tests use i18n keys not hardcoded strings. Accessibility helper uses @axe-core/playwright with wcag2a,wcag2aa tags. Reference: workspaces/adoption-insights/ has a working Playwright setup.

Notes

Boost has only one app (NFS) so no APP_MODE needed. Dev app uses fixtures from fixtures/ai-catalog-fixtures.yaml. CI already runs yarn playwright test for workspaces with a playwright script. Keep initial suite focused on browse page; entity page tests can follow later.

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 2:15 PM UTC · Completed 2:19 PM UTC
Commit: e649ae6 · View workflow run →

[fullsend-ai-coder]

🤖 Code · ❌ Terminated · Started 2:16 PM UTC · Ended 2:31 PM UTC
Commit: e649ae6 · View workflow run →

[fullsend-ai-triage]

Triage Summary

Category: Feature (new E2E test suite) · Severity: Medium · Status: Ready to implement

Problem

The boost workspace lacks end-to-end test coverage. The AI Catalog browse page has unit tests but no integration tests verifying user flows against a real dev server.

Implementation Plan

All work scoped to workspaces/boost/ (workspace root):

New files:

• playwright.config.ts — webServer starts yarn start, testDir e2e-tests, NFS-only (no APP_MODE)
• e2e-tests/ai-catalog-browse.spec.ts — 9 test scenarios covering browse page flows
• e2e-tests/utils/translations.ts — loads i18n keys from plugin ref.ts
• e2e-tests/utils/accessibility.ts — wraps @axe-core/playwright with wcag2a/wcag2aa tags

Modified files:

• package.json — add test:e2e script, install @playwright/test and @axe-core/playwright

Test Scenarios

1. Browse page loads with fixture card grid
2. Search filters cards, URL updates with ?q=
3. Sidebar filter narrows results
4. Multiple filters combine as AND
5. Clear filters restores full grid
6. Card click navigates to entity detail page
7. Empty state on impossible filter combo
8. Pagination controls work
9. axe-core accessibility audit (unfiltered + filtered)

Reference

The workspaces/adoption-insights/ workspace has a working Playwright setup (playwright.config.ts, e2e-tests/) that serves as the structural template. The boost config should be simpler since it only has one app mode (NFS) and no locale matrix.

Notes

• Dev app uses fixtures from fixtures/ai-catalog-fixtures.yaml
• CI already runs yarn playwright test for workspaces with a playwright script
• Initial suite is scoped to browse page only; entity page tests can follow later

---

Labels: Issue already has workspace/boost label. Adding 'feature' for new capability and 'Tests' as this is a test-only change. Adding 'triaged' to reflect completed triage.

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 2:16 PM UTC · Completed 2:31 PM UTC
Commit: e649ae6 · View workflow run →