SKILL DETAIL
Selenium UI Testing(EN)
Need outputs that should land in a Selenium UI testing workflow.
StatusStable
TypeAtomic Skill
DomainSoftware testing
SDLCTest design
Good forQA / DEV
LanguageChinese / English
EvalsEvals ✓
Synced2026-09-15
Why this Skill
It turns this Skill's method into a quality input that can be executed, reviewed, and reused.
- Do not use it with vague scope and no context.
- Do not treat every area as equally important.
When to use
Use this Skill
- Need outputs that should land in a Selenium UI testing workflow.
- The project already uses Selenium or wants Selenium-ready planning.
Common pitfalls
- Do not use it with vague scope and no context.
- Do not treat every area as equally important.
- Do not skip assumptions and missing information.
Input
Minimum Input
- Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
Recommended Input
- Project goal
- Test scope
- Constraints
Optional Context
- Relevant code or configuration
- Historical results
- Logs and metrics
Output
The output follows this Skill's method and makes facts, assumptions, risks, and next steps explicit.
Judge the output value before installing
- 01Open prompts/ui-test-selenium.md and use it as the main prompt.
- 02Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
- 03If the input is incomplete, return a usable first version and mark missing information and assumptions.
How It Works
- 01Open prompts/ui-test-selenium.md and use it as the main prompt.
- 02Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
- 03If the input is incomplete, return a usable first version and mark missing information and assumptions.
Install & Quick Start
Install command / SHELL
npx skills add \
https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/ui-test-selenium
-gui-test-selenium.prompt
@skill ui-test-selenium
Using the current project context, produce an actionable result following this Skill.
Additional context:
[Paste project context or requirement]---
name: ui-test-selenium
description: Use this skill when you need to design Selenium WebDriver UI automation plans with stable locators, waits, Page Objects, Grid, and CI execution; triggers include Selenium UI testing, UI automation testing, and ui-test-selenium.
---
# Selenium UI Testing (EN)
**Chinese version：** See the corresponding Chinese skill.
## When to Use
- Need outputs that should land in a Selenium UI testing workflow.
- The project already uses Selenium or wants Selenium-ready planning.
## Output Format Options
Markdown by default unless the request explicitly asks for another format.
## How to Use
1. Open `prompts/ui-test-selenium.md` and use it as the main prompt.
2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
3. If the input is incomplete, return a usable first version and mark missing information and assumptions.
## Reference Files
- `prompts/ui-test-selenium.md`: main prompt for this skill.
- `references/framework-spec.md`: tool-specific structure and coverage notes.
- `references/setup-and-ci.md`: setup, execution, and CI notes.
- `examples/sample-context.md`: sample request context.
- `scripts/run-tests.sh`: lightweight local execution entry point.
## Common Pitfalls
- Do not use it with vague scope and no context.
- Do not treat every area as equally important.
- Do not skip assumptions and missing information.
## Best Practices
- Start from the prompt file, then add only the context that matters.
- Keep the output risk-driven and executable.
- If the request is incomplete, return a usable first version and mark gaps.