Skip to content
Back to skills

Automation E2e Maintainable Selectors Cypress

ASecurity

Selector strategy and structure choices keeping end-to-end suites maintainable through UI churn.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsbashtestinggitapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aniruddhaadak80/skills --skill automation-e2e-maintainable-selectors-cypress --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Automation E2e Maintainable Selectors Cypress?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Automation E2e Maintainable Selectors Cypress
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aniruddhaadak80-automation-e2e-maintainable-selectors-cypress/badge)](https://www.skillsdirectory.com/skills/aniruddhaadak80-automation-e2e-maintainable-selectors-cypress)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: automation-e2e-maintainable-selectors-cypress
description: "Selector strategy and structure choices keeping end-to-end suites maintainable through UI churn."
---
# Write E2E tests that survive redesigns (Cypress)

> Selector strategy and structure choices keeping end-to-end suites maintainable through UI churn.

**Track:** 🧪 QA & Testing · **Domain:** Test Automation · **Level:** intermediate · **~35 min**

**Who this is for:** QA Engineers, SDETs, Test Automation Engineers, Developers

## When to Use This Skill

Selector strategy and structure choices keeping end-to-end suites maintainable through UI churn.
Use it whenever a matching task appears in conversation — the agent loads these instructions on demand.

## Steps

1. Locate elements by accessible role/name — resilient AND forces a11y
2. Ban generated class names and nth-child position selectors
3. Model flows in helpers once; tests read as user intent scripts
4. Assert observable outcomes (row appears) over DOM internals
5. Seed state via APIs/fixtures, never UI-only setup chains
6. Keep each spec independent: any subset passes on fresh context
7. Avoid conditional control-flow; command determinism wins
8. Intercept network for deterministic state setup

## Common Pitfalls

- Page objects becoming second app full of logic
- Chained UI setups breaking one hop upstream

## Commands

**Install with skills CLI**
```bash
npx skills add aniruddhaadak80/skills --skill automation-e2e-maintainable-selectors-cypress
```

**Install globally**
```bash
npx skills add aniruddhaadak80/skills --skill automation-e2e-maintainable-selectors-cypress -g
```

---

Part of [aniruddhaadak80/skills](https://github.com/aniruddhaadak80/skills) · Browse all at https://skills.sh/aniruddhaadak80/skills

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…