This skill enables Claude to generate end-to-end (E2E) tests for web applications. It leverages Playwright, Cypress, or Selenium to automate browser interactions and validate user workflows. Use this skill when the user requests to "create E2E tests", "generate end-to-end tests", or asks for help with "browser-based testing". The skill is particularly useful for testing user registration, login flows, shopping cart functionality, and other multi-step processes within a web application. It supports cross-browser testing and can be used to verify the responsiveness of web applications on different devices.
89
53%
Does it follow best practices?
Impact
97%
1.00xAverage score across 9 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-batch-20251204-000554/plugins/testing/e2e-test-framework/skills/e2e-test-framework/SKILL.mdDefault Playwright framework selection
Playwright framework used
100%
100%
Playwright config file present
100%
100%
Package.json includes Playwright
100%
100%
Login navigation step
100%
100%
Login element interaction
100%
100%
Login assertion
100%
100%
Profile navigation step
100%
100%
Profile element interaction
100%
100%
Profile assertion
100%
100%
Two separate test files
100%
100%
User-specified framework and workflow assertions
Cypress framework used
100%
100%
cypress.config.js present
100%
100%
Package.json includes Cypress
100%
100%
Product/cart navigation
100%
100%
Cart verification assertion
100%
100%
Discount code step
100%
100%
Shipping/payment interaction
100%
100%
Order total assertion
70%
60%
Order confirmation assertion
100%
100%
Multi-step structure
100%
100%
File in cypress/e2e/ path
100%
100%
Cross-browser test configuration
Multi-browser config
100%
100%
Browsers from supported set
100%
100%
Playwright used by default
100%
100%
Config file present
100%
100%
Package.json with dependencies
100%
100%
Form field interactions
100%
100%
Form submission step
100%
100%
Registration success assertion
100%
100%
Navigation to registration
100%
100%
Selenium framework selection
Selenium library used
100%
100%
No Playwright/Cypress imports
100%
100%
Package.json includes selenium-webdriver
100%
100%
Browser driver instantiation
100%
100%
Navigation step
100%
100%
Element interaction
100%
100%
Assertion present
100%
100%
Driver quit/teardown
100%
100%
Test structure
100%
100%
Responsive device viewport testing
Playwright used by default
100%
100%
Viewport configuration present
100%
100%
Multiple viewport sizes tested
100%
100%
Config file present
100%
100%
Package.json includes Playwright
100%
100%
Navigation step
100%
100%
Element interaction on mobile
100%
100%
Responsive assertion
100%
100%
No device emulation via unsupported browsers
100%
100%
Multi-step workflow assertions
Playwright used by default
100%
100%
Step 1 navigation
100%
100%
Step 1 assertion
100%
100%
Step 2 interaction and assertion
100%
100%
Step 3 form interaction
100%
100%
Final confirmation assertion
100%
100%
At least 4 distinct interaction steps
100%
100%
Assertions not only at end
100%
100%
Config file present
100%
100%
Package.json includes Playwright
100%
100%
Separate test file per concern
100%
100%
Form validation error state assertions
Playwright used by default
100%
100%
playwright.config present
100%
100%
package.json includes Playwright
100%
100%
Navigation step present
100%
100%
Invalid email test case
0%
0%
Empty required field test case
100%
100%
Password validation test case
50%
100%
Error message assertions
100%
100%
Happy path test case
100%
100%
Negative tests NOT skipped at end
100%
100%
Element interaction for each case
100%
100%
Multi-workflow test suite organization
Playwright used by default
100%
100%
playwright.config present
100%
100%
package.json includes Playwright
100%
100%
Login workflow test file
80%
70%
Search or browse workflow test file
100%
100%
Cart or checkout workflow test file
70%
90%
At least 3 separate test files
100%
100%
Navigation in each test
100%
100%
Element interactions in each test
87%
100%
Assertions in each test
100%
100%
Tests in tests/ or e2e/ directory
70%
100%
Cypress cross-browser configuration
Cypress framework used
100%
100%
cypress.config present
100%
100%
package.json includes Cypress
100%
100%
Multi-browser configuration
100%
100%
Browsers from supported set only
100%
100%
Test in cypress/e2e/ directory
100%
100%
Navigation step present
100%
100%
Element interactions present
100%
100%
Assertion present
100%
100%
No Playwright imports
100%
100%
7dedb93
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.