# QSP-39305 — Unit Integration Testing E2E Tests

Add 20 new Playwright E2E tests running against a mocked backend to satisfy the "Unit Integration Testing" scorecard signal (grade A requires ≥ 20 passing tests with zero failures). Two pages had zero coverage before this ticket.

**Commit:** `feat: add E2E tests to satisfy unit integration testing signal QSP-39305`

---

## What Changed

- 20 E2E tests added covering all 4 app pages: header navigation, overview elements, drill-down to aggregation, components list navigation, AppScorePage signal tiles, and the aggregation filter/tab view
- First test coverage for AppScorePage and OverviewAggregationView — both were previously untested
- New Page Objects and Assertion classes created for both untested pages
- Tests run against a mocked backend (`FORCE_LOCAL_DEV_SERVER_IN_CI`), separate from the existing 7 tests that target the real deployed environment

---

## Acceptance Criteria

- AC-1: At least 20 new passing E2E tests are added in `e2e/tests/`
- AC-2: Tests cover all 4 app pages: Overview, Overview Aggregation, Components, AppScorePage
- AC-3: Tests include both single-page (element visibility, URL state) and multi-page (navigation) flows
- AC-4: Tests use `FORCE_LOCAL_DEV_SERVER_IN_CI = 'true'` for mocked backend execution
- AC-5: All tests use `Author.GERALD_SPENLINGWIMMER`, ticket `QSP-39305`, and `TestTag.E2E`
- AC-6: Page Objects and Assertion classes created for AppScorePage and OverviewAggregationView
- AC-7: All tests pass with zero failures
- AC-8: TypeScript compiles cleanly
