Building a Production Framework — quiz

The team's 300-spec project has everything dumped in `cypress/e2e/`. What's a sensible structure as the suite scales?

• Keep it flat — folders just slow you down
• Group by feature/domain: `cypress/e2e/checkout/`, `cypress/e2e/account/`, `cypress/e2e/admin/`. Plus shared `support/` for commands, `pages/` for POMs, `fixtures/` for data, and `factories/` for dynamic data
• One file per app route, no nesting allowed
• Mirror the production source-code tree exactly