Write a Cypress E2E Test for a Complete User Workflow

Write a Cypress end-to-end test spec that validates the complete [WORKFLOW_NAME] user workflow on [APPLICATION_TYPE] (e.g., e-commerce checkout, user registration, dashboard CRUD). The application runs at [BASE_URL] and uses [AUTH_METHOD] for authentication. Workflow steps to test: [LIST_WORKFLOW_STEPS_IN_ORDER] Generate the test spec with these components: 1. **Test Setup (before/beforeEach)**: - Seed test data using cy.request() to call [API_ENDPOINT] or use cy.task() for database seeding - Implement programmatic login via API to skip UI login (store token in localStorage/cookies) - Set viewport to [VIEWPORT_SIZE] and configure baseUrl 2. **Custom Commands**: Define reusable commands in commands.js for: - Login: Cypress.Commands.add('login', ...) - A domain-specific action: [CUSTOM_COMMAND_DESCRIPTION] - Selecting elements using data-testid attributes following the pattern [data-testid="[ELEMENT_PATTERN]"] 3. **Test Cases** (within describe/it blocks): - **Happy Path**: Walk through the entire workflow asserting each page transition, form submission, and success state - **Validation Test**: Submit forms with invalid data and assert error messages appear for [REQUIRED_FIELDS] - **Edge Case**: Test behavior when [EDGE_CASE_SCENARIO] (e.g., network timeout, empty state, duplicate submission) - **Responsive Check**: Verify critical elements at mobile viewport (375x667) 4. **Assertions & Waits**: - Use cy.intercept() to stub or spy on [API_CALLS] and alias them with .as() - Wait for API responses with cy.wait('@alias') before asserting DOM changes - Assert URL changes with cy.url().should('include', '/[EXPECTED_PATH]') - Verify toast notifications, modals, or redirect behavior 5. **Cleanup (after)**: Remove test data via API calls or cy.task() Use best practices: no cy.wait(ms), no hard-coded selectors like .btn-primary, and no conditional testing. Include comments explaining the purpose of each intercept and assertion.