verify-e2e

Name: verify-e2e
Availability: InStock
Author: junnv93

Verify E2E test code compliance and architectural coverage across projects.

Updated Aug 23, 2026

Search Tags:#testing #architecture #e2e #qa #fixtures #locator-patterns

Ready to run

npx skills add https://github.com/junnv93/equipment_management_system --skill verify-e2e

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-e2e
Source: https://github.com/junnv93/equipment_management_system/tree/main/.claude/skills/verify-e2e
Command: npx skills add https://github.com/junnv93/equipment_management_system --skill verify-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verifies that E2E test code adheres to defined patterns and architecture-level checks, helping teams maintain consistent, reliable end-to-end validation across projects.

Core Features & Use Cases

Validates auth fixture usage (storageState-based authentication patterns) and enforces strict login isolation.
Enforces locator patterns, SSOT constants, and test isolation to reduce flakiness.
Verifies architecture coverage such as CAS VERSION_CONFLICT scenarios, cache invalidation after mutations, and site access control on mutations.

Quick Start

Run verify-e2e after adding or modifying E2E specs to ensure architectural coverage.

Frequently Asked Questions about verify-e2e

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

FAQPage Schema

How do I enforce E2E test isolation and prevent flakiness in frontend and backend test suites?▼

Enforce E2E test isolation by validating auth fixtures, locator usage, and SSOT constants. This verifies strict login isolation and architecture-level checks to reduce flakiness across frontend and backend test suites.

How does storageState-based authentication work for E2E test fixtures?▼

StorageState-based authentication validates auth fixture usage for E2E tests by enforcing strict login isolation. This ensures consistent authentication patterns across the project's frontend and backend test suites.

What's the best way to validate architecture coverage in E2E tests after mutations?▼

Validate architecture coverage in E2E tests by checking cache invalidation after mutations, CAS VERSION_CONFLICT scenarios, and site access control. This enforces step-by-step validation with references and workflow steps.

Do I need to run E2E architecture checks in serial mode for state-changing tests?▼

Yes, state-changing E2E tests require serial mode execution discipline. Verifying execution discipline ensures that architecture-level checks and mutation validations run sequentially to prevent state conflicts.

Can I verify locator patterns and SSOT constants across existing E2E specs?▼

Yes, you can verify locator patterns and SSOT constants across existing E2E specs. Running verification after adding or modifying E2E specs ensures architectural coverage and compliance with defined patterns.