skills.rest
yaresimeonthomas
yaresimeonthomasCOMMUNITY
Explore all skills by this author →
GitHub

e2e-conventions

Enforce consistent e2e test coverage for Atomic CRM UI changes.

Updated Jul 1, 2026
Search Tags:#UI testing#frontend testing#playwright#e2e testing#test conventions#test verification#test placement
One-click install
npx skills add https://github.com/yaresimeonthomas/-kate-crm --skill e2e-conventions-yaresimeonthomas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-conventions
Source: https://github.com/yaresimeonthomas/-kate-crm/tree/main/.claude/skills/e2e-conventions
Command: npx skills add https://github.com/yaresimeonthomas/-kate-crm --skill e2e-conventions-yaresimeonthomas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves inconsistent e2e test coverage, misplaced test files, and unclear verification standards for user-facing changes in the Atomic CRM project, reducing review friction and ensuring all critical user interactions are properly tested.

Core Features & Use Cases

  • Clear Test Requirement Rules: Explicitly defines which changes mandate e2e tests (UI components, filters, forms, user interactions) and valid exceptions (pure CSS updates, database-only migrations).
  • Standardized File Organization: Specifies exact naming and placement conventions for e2e test specs under the e2e/ directory, with optional ticket ID prefixes for easy traceability to project tasks.
  • Verification Checklists: Provides actionable checklists for code reviewers and CI pipelines to confirm tests assert correct user-visible behavior and follow project standards.
  • Use Case: When a developer adds a new deal importance filtering feature to the CRM, this skill guides them to create a correctly named e2e spec (e.g., e2e/TASK-001-deal-importance.spec.ts) that verifies the filter works as expected for end users.

Quick Start

Reference this e2e-conventions skill whenever you implement or modify UI components, filters, forms, or user interactions to confirm e2e test requirements and follow project testing standards.

Frequently Asked Questions about e2e-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When do I need to write e2e tests for UI changes?▼

E2e tests are required for UI changes involving components, filters, search functionality, forms, and user input handling. Pure CSS updates and database-only migrations are explicitly exempted from these e2e testing requirements.

How do I name and place e2e test files for frontend testing?▼

Place e2e test files under the e2e/ directory using a .spec.ts extension. You can prefix the filename with an optional ticket ID, like e2e/TASK-001-feature.spec.ts, to ensure traceability to project tasks.

What should e2e tests verify for user-facing features?▼

E2e tests must include explicit assertions for correct user-visible behavior. Verification checklists are provided for code reviewers and CI pipelines to confirm tests validate actual user interactions rather than just technical operations.

Does this e2e testing convention work for Playwright specs?▼

Yes, this convention standardizes Playwright e2e testing by enforcing consistent test placement, naming conventions, and required user-visible assertions for frontend testing within the Atomic CRM project.

What are the limitations of using standard e2e test conventions?▼

These e2e test conventions apply specifically to user-facing changes and do not cover pure CSS updates or database-only migrations. They focus on standardizing test file placement, naming, and verification checklists for UI components.

Related Skills

Explore More Software Engineering Skills→
ggombeeggombee
13

setup-e2e

Automates Playwright E2E testing environment setup for web applications.

Community
Intermediate
hffmnnjhffmnnj
39

testing

Automate unit, integration, and E2E tests in JavaScript/TypeScript projects.

Community
Intermediate
mohitmishra786mohitmishra786

test

Generate unit, integration, and end-to-end tests with Pytest, Jest, Playwright, and k6.

Community
Advanced
fgarofalo56fgarofalo56
6

cypress

Automate end-to-end web application testing with Cypress.

Community
Advanced