running-e2e-tests

# E2E Test Framework ## Current State !`cat package.json 2>/dev/null | grep -oE 'playwright|cypress|selenium' || echo 'No E2E framework detected'` ## Overview Execute end-to-end tests that simulate real user workflows across the full application stack -- browser interactions, API calls, database operations, and third-party integrations. Supports Playwright (recommended), Cypress, Selenium, and Puppeteer. ## Prerequisites - E2E testing framework installed (Playwright, Cypress, or Selenium WebDriver) - Application running in a test environment with seeded test data - Browser binaries installed (`npx playwright install` or Cypress binary) - Test user accounts created with known credentials - Environment variables configured for base URL, API keys, and test credentials ## Instructions 1. Identify critical user journeys to cover: - User registration and login flow. - Primary feature workflow (e.g., create item, edit, delete). - Search and filtering functionality. - Checkout or payment flow (if applicable). - Error handling (404 pages, form validation, session expiry). 2. Create page object models (POM) for reusable page interactions: - One class per page or major component. - Encapsulate locators, actions (click, fill, select), and assertions. - Use `data-testid` attributes as primary selectors for stability. 3. Write E2E test files organized by user journey: - Each test file covers one complete workflow. - Use `beforeEach` to navigate to the s...