c3f43d8b61
- Add 60 new agents across all 10 categories (75 -> 135) - Add 95 new plugins with command files (25 -> 120) - Update all agents to use model: opus - Update README with complete plugin/agent tables - Update marketplace.json with all 120 plugins
1.4 KiB
1.4 KiB
/record-test - Record New E2E Test
Record user interactions to generate an end-to-end test file.
Steps
- Ask the user for the test name and the user flow to record (e.g., "login flow", "checkout process")
- Determine the e2e framework in use from the project configuration
- Identify the base URL and starting page for the recording session
- For Playwright: use
npx playwright codegenwith the target URL - For Cypress: set up Cypress Studio or guide manual recording
- Capture the generated test code from the recording session
- Clean up the recorded code: add proper assertions, remove redundant waits
- Add descriptive test names and group related interactions into logical steps
- Add page object references if the project uses the Page Object Model pattern
- Save the test file to the appropriate directory with the correct naming convention
- Run the newly created test to verify it passes
- Report the result and suggest additional assertions to strengthen the test
Rules
- Follow the project's existing test naming conventions
- Use data-testid selectors over CSS selectors when available
- Add at least one assertion per user interaction step
- Include setup and teardown hooks if the test requires authentication
- Do not hardcode test data; use fixtures or environment variables
- Keep recorded tests under 50 lines; split longer flows into separate tests