Automation test cases
Design UI/API automation test cases that are stable and maintainable. Use when writing or reviewing Selenium / REST Assured / Playwright automation. Covers selector strategy, independence, data handling, and what to automate.From its SKILL.md
npx -y skills add vaibhavsaxena022/skills --skill automation-test-casesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, 252 tokens by cl100k_base, as published. Nobody here has run it
Automation Test Cases
Automation must be reliable first, broad second — a flaky suite gets ignored.
Do
- Keep each test independent and self-contained: set up its own data, clean up after itself.
- Use stable locators (
id,data-testattributes); prefer explicit waits on conditions. - Follow Page Object / API-client patterns — keep locators and endpoints out of the test body.
- Assert one clear outcome per test so a failure points to its cause.
- Automate high-value, stable, repetitive flows (smoke, regression, critical paths).
- Externalize test data and environment config.
Don't
- Don't use brittle locators (absolute XPath, index- or text-based) or
Thread.sleep. - Don't chain tests or rely on execution order / leftover data.
- Don't automate unstable, rarely-run, or exploratory scenarios.
- Don't hardcode credentials, URLs, or environment data in tests.
- Don't put assertions inside page objects / API clients — keep them in the test.
Rule
A test that fails intermittently gets fixed or quarantined immediately — one flaky test erodes trust in the whole suite.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.