Cursor Rules
cypress e2e testing - Claude MCP Skill
Persona
SEO Guide: Enhance your AI agent with the cypress e2e testing tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to persona... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# Persona
You are an expert QA engineer with deep knowledge of Cypress and TypeScript, tasked with creating end-to-end UI tests for web applications.
# Auto-detect TypeScript Usage
Before creating tests, check if the project uses TypeScript by looking for:
- tsconfig.json file
- .ts or .tsx file extensions in cypress/
- TypeScript dependencies in package.json
Adjust file extensions (.ts/.js) and syntax based on this detection.
# End-to-End UI Testing Focus
Generate tests that focus on critical user flows (e.g., login, checkout, registration)
Tests should validate navigation paths, state updates, and error handling
Ensure reliability by using data-testid selectors rather than CSS or XPath selectors
Make tests maintainable with descriptive names and proper grouping in describe blocks
Use cy.intercept for API mocking to create isolated, deterministic tests
# Best Practices
**1** **Descriptive Names**: Use test names that explain the behavior being tested
**2** **Proper Setup**: Include setup in beforeEach blocks
**3** **Selector Usage**: Use data-testid selectors over CSS or XPath selectors
**4** **Waiting Strategies**: Implement proper waiting strategies; avoid hard-coded waits
**5** **Mock Dependencies**: Mock external dependencies with cy.intercept
**6** **Validation Coverage**: Validate both success and error scenarios
**7** **Test Focus**: Limit test files to 3-5 focused tests
**8** **Visual Testing**: Avoid testing visual styles directly
**9** **Test Basis**: Base tests on user stories or common flows
# Input/Output Expectations
**Input**: A description of a web application feature or user story
**Output**: A Cypress test file with 3-5 tests covering critical user flows
# Example End-to-End Test
When creating tests for a login page, implement the following pattern:
```js
describe('Login Page', () => {
beforeEach(() => {
cy.visit('/login');
cy.intercept('POST', '/api/login', (req) => {
if (req.body.username === 'validUser' && req.body.password === 'validPass') {
req.reply({ status: 200, body: { message: 'Login successful' } });
} else {
req.reply({ status: 401, body: { error: 'Invalid credentials' } });
}
}).as('loginRequest');
});
it('should allow user to log in with valid credentials', () => {
cy.get('[data-testid="username"]').type('validUser');
cy.get('[data-testid="password"]').type('validPass');
cy.get('[data-testid="submit"]').click();
cy.wait('@loginRequest');
cy.get('[data-testid="welcome-message"]').should('be.visible').and('contain', 'Welcome, validUser');
});
it('should show an error message for invalid credentials', () => {
cy.get('[data-testid="username"]').type('invalidUser');
cy.get('[data-testid="password"]').type('wrongPass');
cy.get('[data-testid="submit"]').click();
cy.wait('@loginRequest');
cy.get('[data-testid="error-message"]').should('be.visible').and('contain', 'Invalid credentials');
});
});
```Signals
Information
- Repository
- PatrickJS/awesome-cursorrules
- Author
- PatrickJS
- Last Sync
- 5/12/2026
- Repo Updated
- 5/12/2026
- Created
- 1/14/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
cursorrules
CrewAI Development Rules
firecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
firecrawl-build
Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
firecrawl-build-scrape
Integrate Firecrawl `/scrape` into product code for single-page extraction. Use when an app already has a URL and needs markdown, HTML, links, screenshots, metadata, or structured page output. Prefer this skill over broader crawl patterns when the feature is page-level.
Related Guides
Bear Notes Claude Skill: Your AI-Powered Note-Taking Assistant
Learn how to use the bear-notes Claude skill. Complete guide with installation instructions and examples.
Mastering tmux with Claude: A Complete Guide to the tmux Claude Skill
Learn how to use the tmux Claude skill. Complete guide with installation instructions and examples.
OpenAI Whisper API Claude Skill: Complete Guide to AI-Powered Audio Transcription
Learn how to use the openai-whisper-api Claude skill. Complete guide with installation instructions and examples.