AGENT SKILL

test-scenario-designer

Derive high-level test scenarios from a requirement or acceptance criteria before anyone writes detailed steps. Use when a tester says "what scenarios should we test", "design scenarios for this feature", or pastes ACs and wants coverage mapped out. Produces positive, negative, boundary, and cross-role scenarios, each tagged by risk and traced back to the AC it exercises, then stops for review before test cases are written.

License 许可
MIT
最近更新
2026-07-15
Stars
★ 4
Forks
8

01 前言 Front Matter

name
test-scenario-designer
license
MIT
metadata
{ "author": "TheTestingAcademy", "version": "1.0.0", "stlc-phase": "Test Design" }
description
Derive high-level test scenarios from a requirement or acceptance criteria before anyone writes detailed steps. Use when a tester says "what scenarios should we test", "design scenarios for this feature", or pastes ACs and wants coverage mapped out. Produces positive, negative, boundary, and cross-role scenarios, each tagged by risk and traced back to the AC it exercises, then stops for review before test cases are written.

03 SKILL.md 正文

Test Scenario Designer

You turn requirements into a coverage map — the set of things worth testing — one level above step-by-step cases. Breadth and traceability matter more than detail here.

When to use

  • ACs or a feature description exist and you need the "what could go right/wrong" list.
  • You want coverage agreed and reviewed before investing in detailed test cases.
  • A reviewer asks "did we think about the negative and boundary paths?"

Workflow

  1. Read the source. Take the requirement, ACs, or analyzer output. If it is too vague to derive scenarios, say so and route back to requirement analysis — do not guess intent.
  2. Enumerate by category. For each AC, generate scenarios across: positive (happy path), negative (invalid input, errors, permissions denied), boundary (empty, min, max, limits), and cross-role / cross-state (different personas, concurrent or interrupted flows).
  3. Tag risk. Mark each scenario P0/P1/P2 by likelihood × impact. Note non-functional angles (perf, security, a11y, i18n) where relevant.
  4. Trace. Map every scenario to the AC or gap it covers; flag ACs with zero scenarios and any scenario that maps to no requirement.
  5. HUMAN REVIEW GATE (mandatory). Present as a draft coverage set. Call out assumptions and any area you deliberately left out. Ask for confirmation before it is handed to the test-case-writer; do not expand into detailed steps yourself until approved.

Output shape

## Test Scenarios — <feature / JIRA-KEY>
| ID   | Scenario                      | Type      | Risk | Covers AC |
| TS-1 | ...                           | positive  | P0   | AC-1      |
| TS-2 | ...                           | negative  | P1   | AC-1      |
| TS-3 | ...                           | boundary  | P2   | AC-2      |
Coverage note: ACs with no scenario / scenarios with no AC
--- HUMAN REVIEW GATE ---
Assumptions / Deliberate exclusions / "Approve before test cases are written"

Guardrails

  • Do not invent requirements to justify a scenario — an untraceable scenario is a flag.
  • Scenarios stay high-level; leave preconditions, steps, and data to the test-case-writer.
  • Never present the set as complete coverage — a human confirms nothing important is missing.
  • If the source is too ambiguous to design against, stop and ask rather than fill gaps.

04 同仓库更多 Skills

PramodDutta
PramodDutta/skillmasterclass

se-wait-fixer

Scans Selenium Java code for Thread.sleep and for implicit+explicit wait mixing, then replaces them with WebDriverWait/ExpectedConditions or FluentWait to fix synchronization. Use when an SDET says "remove Thread.sleep from my tests", "fix the flaky waits", "my implicit and explicit waits conflict", or pastes code full of hard sleeps. Produces refactors the engineer must run and confirm.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-test-generator

Generates a runnable Selenium 4 + TestNG test in Java from a plain-language scenario, using explicit waits and stable locators. Use when an SDET says "write a Selenium test for login", "generate a TestNG test for the checkout flow", "automate this scenario in Selenium", or pastes Gherkin/steps and wants Java WebDriver code. Produces a draft test the engineer must review and run.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-report-integrator

Integrates reporting (Allure or ExtentReports) into a Selenium + TestNG suite with listeners, screenshot-on-failure, and step logging. Use when an SDET says "add Allure to my tests", "set up ExtentReports", "capture a screenshot on failure", "add a TestNG listener for reporting", or wants readable run reports. Produces listener and config code the engineer must run to generate a report.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-page-object-builder

Builds a Page Object Model class in Java (PageFactory @FindBy or explicit locators) with action methods and a WebDriverWait for a given page. Use when an SDET says "create a page object for the login page", "build a POM class", "refactor these locators into a page object", or pastes a page's fields and wants a reusable POM. Produces a draft class the engineer must review and run.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-locator-strategist

Recommends and repairs Selenium locator strategy — replaces brittle absolute XPath with By.id, By.cssSelector, or Selenium 4 relative locators, and explains the trade-offs. Use when an SDET says "this XPath keeps breaking", "make this locator more stable", "why is my locator flaky", "convert this XPath to CSS", or pastes selectors to harden. Produces proposals the engineer must verify in the DOM.

★ 4
PramodDutta
PramodDutta/skillmasterclass

se-grid-configurator

Configures Selenium Grid 4 (hub-and-node or standalone, including Docker) and wires RemoteWebDriver for parallel and distributed runs. Use when an SDET says "set up Selenium Grid", "run my tests on a remote grid", "dockerize Selenium Grid 4", "point my tests at RemoteWebDriver", or wants parallel execution across nodes. Produces config and code the engineer must run and validate in their environment.

★ 4