debug-cypress

Diagnose Cypress test failures by locating failing selectors and assertions.

164|44|Updated Jun 30, 2023

Search Tags:#testing #debugging #investigation #qa #cypress #ci

Ready to run

npx skills add https://github.com/hivemq/hivemq-edge --skill debug-cypress

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-cypress
Source: https://github.com/hivemq/hivemq-edge/tree/main/hivemq-edge-frontend/.claude/skills/debug-cypress
Command: npx skills add https://github.com/hivemq/hivemq-edge --skill debug-cypress

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineers diagnose Cypress test failures by guiding a structured, repeatable investigation instead of guessing.

Core Features & Use Cases

Guided error analysis for Cypress failures, including element not found, expected to find element, and assertion errors.
Step-by-step protocol to locate the failing selector in source code, inspect implementation, and verify test structure.
Recommendations on when not to use force, cy.wait(), or rewriting tests, and how to leverage existing Page Object Models.

Quick Start

Describe the exact error you are seeing and follow the guided investigation steps to pinpoint the source of the failure.

Frequently Asked Questions about debug-cypress

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

FAQPage Schema

How do I debug Cypress test failures when selectors are not found?▼

Debug Cypress selector failures by following a structured investigation protocol that reads the error, locates the failing selector in source code, inspects the implementation, and verifies test structure using Bash and Grep.

Why does my Cypress assertion fail and how can I pinpoint the cause?▼

Cypress assertion failures require deterministic investigation that locates the implementation, resolves translations if used, checks the Page Object Model, and points to precise commands to identify the exact source of the failure.

What is the best way to investigate Cypress CI failures without rewriting tests?▼

Investigate Cypress CI failures by executing a repeatable protocol that reads the error, locates the implementation, and verifies test structure before resorting to force actions, cy.wait(), or rewriting the test.

When should I not use force or cy.wait() in Cypress debugging?▼

Avoid using force or cy.wait() in Cypress debugging until a structured investigation checks the Page Object Model, resolves translations, and inspects source code to pinpoint the actual failure source safely.

Can I use this guided investigation for locally running Cypress tests and CI scenarios?▼

Yes, the guided investigation protocol applies to both locally running Cypress tests and CI scenarios, ensuring a deterministic approach to diagnosing selector and assertion failures across environments.

How do I locate a failing Cypress selector in source code?▼

Locate a failing Cypress selector by using Grep and Glob to search source code, inspecting the implementation, resolving translations if used, and verifying the Page Object Model structure.