What problem does it solve? Writing Flutter integration tests and Playwright E2E tests requires knowing the exact keys, finder expressions, and ARIA semantic labels for every interactive widget, which are otherwise scattered across the codebase and easy to get wrong. ## Core Features & Use Cases - Flutter Key Reference: Provides a lookup table of widget keys (e.g., login_email_field, home_add_product_button) with their underlying widget types for integration_test finders. - Playwright Selector Map: Documents the kebab-case semantic label convention (btn-*, input-*, chk-*, link-*) and maps every screen widget to its Playwright selector via getByRole and aria-label locators. - Testing Conventions: Captures project-specific rules such as using pump loops instead of pumpAndSettle(), one testWidgets per file, and force-enabled semantics in main.dart. - Use Case: When writing an E2E test for the checkout flow, look up btn-place-order and chk-terms-accepted to interact with the Place Order button and terms checkbox without inspecting the Flutter source. ## Quick Start Ask the AI to write a Playwright E2E test that logs in, adds a product to the cart, and completes checkout using the widget-finders selectors.
