tessl-labs/cypress-testing
Cypress E2E testing patterns -- selectors, cy.intercept, cy.session, cy.clock, custom commands, test isolation, and anti-patterns
98
99%
Does it follow best practices?
Impact
97%
1.25xAverage score across 4 eval scenarios
Passed
No known issues
Evaluation results
100%
25%E2E Tests for Login Flow and Dashboard
cy.session for auth caching
0%
100%
Login custom command
100%
100%
data-testid selectors
35%
100%
cy.intercept with aliases
100%
100%
beforeEach test isolation
100%
100%
No arbitrary waits
100%
100%
Login error state tested
100%
100%
baseUrl in config
100%
100%
URL assertion after login
100%
100%
93%
3%E2E Tests for a Multi-Step Form Wizard
beforeEach test isolation
100%
100%
No conditional testing
64%
71%
data-testid selectors
58%
100%
baseUrl in config
100%
100%
cy.intercept for form submission
100%
100%
Custom command for step navigation
100%
100%
Validation error testing
100%
70%
No arbitrary waits
100%
100%
Back navigation tested
100%
100%
98%
41%E2E Tests for Search with Debounced Input and Filters
cy.clock and cy.tick for debounce
0%
100%
cy.intercept with aliases for search API
100%
100%
No conditional testing
41%
100%
Empty state tested
100%
100%
data-testid selectors
40%
100%
Fixture data for deterministic results
100%
100%
beforeEach test isolation
87%
75%
No arbitrary waits
0%
100%
Filter interaction tested
100%
100%
baseUrl in config
100%
100%
100%
13%E2E Tests for Shopping Cart and Checkout
cy.intercept with aliases for API calls
100%
100%
Fixture data for API stubbing
58%
100%
Custom commands for repeated flows
33%
100%
data-testid selectors
100%
100%
Form validation tested
100%
100%
beforeEach test isolation
100%
100%
No arbitrary waits
100%
100%
Error state coverage
100%
100%
baseUrl in config
100%
100%
Empty cart state tested
100%
100%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6