Record user interactions and generate Playwright/Cypress test scripts automatically.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add mediar-ai/skillhubz --skill e2e-test-recorder --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of E2e Test Recorder?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mediar-ai-e2e-test-recorder)More formats (shields.io, HTML) on the badges page.
# E2E Test Recorder
Record user interactions and generate Playwright/Cypress test scripts automatically.
## Prerequisites
- Chrome browser installed
- Target web application accessible
- Desired test framework specified (Playwright or Cypress)
## Instructions
1. Open Chrome and navigate to the starting URL provided by user
2. Begin recording mode:
- Note the initial URL and page state
- Prepare to capture all user interactions
3. Guide user through the test scenario:
- Ask user to describe what they want to test
- Confirm the expected flow (e.g., "login -> dashboard -> create item")
4. For each user interaction, capture:
a. Click events:
- Element selector (prefer data-testid, then role, then CSS)
- Element text content for verification
- Position on page
b. Type events:
- Target input field selector
- Text being entered (mask passwords)
- Any special keys (Enter, Tab)
c. Navigation events:
- New URLs visited
- Page load confirmations
d. Assertions to add:
- Visible text confirmations
- Element presence checks
- URL validations
5. After user completes the flow, generate test code:
For Playwright:
```typescript
test('descriptive test name', async ({ page }) => {
await page.goto('starting-url');
await page.click('[data-testid="button"]');
await expect(page.locator('text=Success')).toBeVisible();
});
```
For Cypress:
```javascript
describe('Test Suite', () => {
it('descriptive test name', () => {
cy.visit('starting-url');
cy.get('[data-testid="button"]').click();
cy.contains('Success').should('be.visible');
});
});
```
6. Output the generated test file and provide instructions for running it
## Error Handling
- If element has no good selector, suggest adding data-testid
- If page has dynamic content, add appropriate waits
- If authentication is needed, generate login helper
## Notes
- Generated tests use best practices for selectors
- Includes automatic wait handling for async operations
- Add custom assertions by describing what to verify
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!