automation-testing
Use this skill when you need to design automation testing approaches using patterns like POM, data-driven testing, or BDD; triggers include automation testing and test automation strategy.
Install
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/automation-testing
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
git clone https://github.com/naodeng/awesome-qa-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.
README
Automation Testing
Skill Overview
Need help with automation testing in a real project context; Need an output that can be used directly for execution, review, or follow-up.
How to Use
- Open
SKILL.mdin this folder and confirm this skill fits your task. - In your AI tool, call
@skill automation-testing, then add your real project context and goal. - If you need a specific output format (table, checklist, report), include it directly in your request.
One-Click Install Script
Run from the repository root:
macOS / Linux
bash ./scripts/install-skills-mac.sh --tool codex --lang en --skill automation-testing
Windows PowerShell
powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill automation-testing
Skill manifest
Automation Testing (English)
Chinese version: See the corresponding Chinese skill.
When to Use
- Need help with automation testing in a real project context.
- Need an output that can be used directly for execution, review, or follow-up.
Workflow
- Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
- Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
- If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
- Default to Markdown; switch formats only when the user asks.
Domain Execution Essentials
- Select using candidate flow | protection obligation | repeat-frequency evidence | oracle/observability | isolation/cleanup | stability | maintenance constraint | adopt/defer rationale. Keep ROI cost scenarios separate; returns cannot remedy missing oracles or authority.
- Reuse the existing framework. First require observable postconditions, independent data, and a CI entry that propagates failure. Defer unmet candidates with unblock conditions.
- Specify unique identities/business keys, setup, actions, business postconditions, failure signal, and teardown. Failed assertions must fail runner/CI, not merely log.
- Separate candidate selection, generated assets, real runs, and business acceptance. Rapidly changing prototypes or non-isolatable real payments may need Human/controlled verification, with evidence-based tradeoffs.
Core Constraints
- Prioritize by risk / business impact — do not treat everything equally.
- Separate confirmed facts from current assumptions.
- Do not invent endpoints, fields, environments, or root causes the user did not provide.
- Keep output executable: concrete scenarios, clear priority, clear next steps.
Progressive Disclosure
When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.
Before producing output, read and follow
prompts/automation-testing.md(minimum coverage, output structure, quality bar).When Excel/CSV/JSON/Word is requested: read
output-formats.mdand honor the format.When a ready-made template fits: use matching files under
output-templates/.For deep framework/troubleshoot/schema notes: read only the relevant file(s) under
references/, do not load the whole directory.For format conversion or helper checks: prefer existing
scripts/over reinventing.For evaluating/regressing this skill: use
evals/with skill-up.
Pre-delivery Checklist
- Followed the main prompt's output structure
- Minimum coverage focus: scope and objective, automation candidates, manual-only areas, priority by risk and ROI, framework alignment, data and environment needs, flaky-test risks, CI or execution strategy, ... (details in main prompt)
- Covered the minimum checklist, or explained omissions
- High-risk items have explicit priority
- Did not invent details the user did not provide
- Assumptions and gaps are marked
Common Pitfalls
- Do not pretend completeness when scope/context is missing.
- Do not treat every item as equally important.
- Do not skip assumptions and information gaps.
- Do not dump generic theory unrelated to the current toolchain.
Files (awesome-qa-skills)
-
agents
-
openai.yaml 467 B
Loading…
-
-
evals
-
cases
-
basic-success.yaml 767 B
Loading… -
domain-method-regression.yaml 1.5 KB
Loading… -
edge-domain-boundary.yaml 774 B
Loading… -
edge-incomplete-input.yaml 707 B
Loading…
-
-
fixtures
-
check-domain-decisions.sh 95 B
Loading… -
check_domain_decisions.py 3.7 KB
Loading… -
domain-oracle.json 153 B
Loading…
-
-
eval.yaml 607 B
Loading…
-
-
output-templates
-
template-csv.csv 206 B · in bundle
-
template-excel.tsv 358 B · in bundle
-
template-json.json 393 B
Loading… -
template-markdown.md 250 B
Loading… -
template-word.md 302 B
Loading… -
template-xmind.md 317 B
Loading…
-
-
prompts
-
automation-testing.md 2.7 KB
Loading…
-
-
references
-
local
-
testing-types-automation-testing-examples-selenium-pom-python-README.md 608 B
Loading…
-
-
domain-decision-example.md 1.7 KB
Loading… -
troubleshooting.md 2.6 KB
Loading…
-
-
scripts
-
batch_convert_templates.py 2.7 KB
Loading… -
convert_formats.py 10.2 KB
Loading… -
convert_output_formats.py 255 B
Loading… -
convert_to_csv.py 270 B
Loading… -
convert_to_excel.py 272 B
Loading… -
convert_to_json.py 271 B
Loading… -
convert_to_markdown.py 275 B
Loading… -
convert_to_word.py 271 B
Loading… -
convert_to_xmind.py 272 B
Loading… -
parse_csv.py 272 B
Loading… -
parse_excel.py 274 B
Loading… -
parse_formats.py 5.3 KB
Loading… -
parse_json.py 273 B
Loading… -
parse_markdown.py 277 B
Loading… -
parse_output_formats.py 253 B
Loading… -
parse_word.py 273 B
Loading… -
parse_xmind.py 274 B
Loading… -
xlsx_reader.py 5.2 KB
Loading…
-
-
output-formats.md 401 B
Loading… -
quick-start.md 2.2 KB
Loading… -
README.md 820 B
# Automation Testing ## Skill Overview Need help with automation testing in a real project context; Need an output that can be used directly for execution, review, or follow-up. ## How to Use 1. Open `SKILL.md` in this folder and confirm this skill fits your task. 2. In your AI tool, call `@skill automation-testing`, then add your real project context and goal. 3. If you need a specific output format (table, checklist, report), include it directly in your request. ## One-Click Install Script Run from the repository root: ### macOS / Linux ```bash bash ./scripts/install-skills-mac.sh --tool codex --lang en --skill automation-testing ``` ### Windows PowerShell ```powershell powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill automation-testing ``` -
SKILL.md 3.9 KB
--- name: automation-testing description: Use this skill when you need to design automation testing approaches using patterns like POM, data-driven testing, or BDD; triggers include automation testing and test automation strategy. license: PolyForm-Noncommercial-1.0.0 metadata: version: "1.0.0" compatibility: "" author: "Awesome QA Skills contributors" language: "en" category: "testing-types" source: "https://github.com/naodeng/awesome-qa-skills" license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0" --- # Automation Testing (English) **Chinese version:** See the corresponding Chinese skill. ## When to Use - Need help with automation testing in a real project context. - Need an output that can be used directly for execution, review, or follow-up. ## Workflow 1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar). 2. Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable. 3. If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps. 4. Default to Markdown; switch formats only when the user asks. ## Domain Execution Essentials 1. Select using candidate flow | protection obligation | repeat-frequency evidence | oracle/observability | isolation/cleanup | stability | maintenance constraint | adopt/defer rationale. Keep ROI cost scenarios separate; returns cannot remedy missing oracles or authority. 2. Reuse the existing framework. First require observable postconditions, independent data, and a CI entry that propagates failure. Defer unmet candidates with unblock conditions. 3. Specify unique identities/business keys, setup, actions, business postconditions, failure signal, and teardown. Failed assertions must fail runner/CI, not merely log. 4. Separate candidate selection, generated assets, real runs, and business acceptance. Rapidly changing prototypes or non-isolatable real payments may need Human/controlled verification, with evidence-based tradeoffs. ## Core Constraints - Prioritize by risk / business impact — do not treat everything equally. - Separate confirmed facts from current assumptions. - Do not invent endpoints, fields, environments, or root causes the user did not provide. - Keep output executable: concrete scenarios, clear priority, clear next steps. ## Progressive Disclosure - When calibrating domain outcomes, valid controls, or evidence gaps, read [references/domain-decision-example.md](references/domain-decision-example.md) for sanitized input, per-item oracles, and reproducible calculations. - Before producing output, read and follow `prompts/automation-testing.md` (minimum coverage, output structure, quality bar). - When Excel/CSV/JSON/Word is requested: read `output-formats.md` and honor the format. - When a ready-made template fits: use matching files under `output-templates/`. - For deep framework/troubleshoot/schema notes: read only the relevant file(s) under `references/`, do not load the whole directory. - For format conversion or helper checks: prefer existing `scripts/` over reinventing. - For evaluating/regressing this skill: use `evals/` with skill-up. ## Pre-delivery Checklist - [ ] Followed the main prompt's output structure - [ ] Minimum coverage focus: scope and objective, automation candidates, manual-only areas, priority by risk and ROI, framework alignment, data and environment needs, flaky-test risks, CI or execution strategy, ... (details in main prompt) - [ ] Covered the minimum checklist, or explained omissions - [ ] High-risk items have explicit priority - [ ] Did not invent details the user did not provide - [ ] Assumptions and gaps are marked ## Common Pitfalls - Do not pretend completeness when scope/context is missing. - Do not treat every item as equally important. - Do not skip assumptions and information gaps. - Do not dump generic theory unrelated to the current toolchain. -
tutorial.md 4.1 KB
Loading…
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.