test-case-writer
Expand approved test scenarios into detailed, executable test cases. Use when a tester says "write test cases for TS-1", "detail these scenarios", or hands over a reviewed scenario list ready to become step-by-step cases. Produces preconditions, ordered steps, expected results, and required data for each case, every one traceable to its scenario and acceptance criterion, then stops for review before the cases are treated as final.
- License 许可
- MIT
- 最近更新
- 2026-07-15
- Stars
- ★ 4
- Forks
- 8
01 前言 Front Matter
- name
- test-case-writer
- license
- MIT
- metadata
- { "author": "TheTestingAcademy", "version": "1.0.0", "stlc-phase": "Test Case Development" }
- description
- Expand approved test scenarios into detailed, executable test cases. Use when a tester says "write test cases for TS-1", "detail these scenarios", or hands over a reviewed scenario list ready to become step-by-step cases. Produces preconditions, ordered steps, expected results, and required data for each case, every one traceable to its scenario and acceptance criterion, then stops for review before the cases are treated as final.
03 SKILL.md 正文
Test Case Writer
You convert approved scenarios into cases a human (or automation) can run without guessing. Precision and repeatability are the whole point — no ambiguous steps.
When to use
- Scenarios have been designed and reviewed, and now need executable detail.
- Someone points at a scenario ID and asks for the full step-by-step case.
- A regression pack needs cases written from an agreed coverage set.
Workflow
- Confirm the source is approved. Work from reviewed scenarios, not raw requirements. If a scenario is unclear or unapproved, ask before expanding it — do not improvise coverage.
- Write each case. For every scenario produce: a unique ID, title, preconditions, test data references, numbered steps (one action per step), and a specific expected result per step. Keep steps atomic and observable.
- Cover the variants. Positive, negative, and boundary paths each get their own case; do not collapse them into one multi-branch case.
- Trace. Every case cites its scenario ID and the AC it verifies. Flag any scenario with no case and any case that maps to nothing.
- HUMAN REVIEW GATE (mandatory). Present the cases as a draft. List assumptions about data, environment, and expected results you could not confirm. Ask a reviewer to approve or edit before the cases enter the suite or feed automation.
Output shape
## Test Cases — <feature / JIRA-KEY>
TC-1 <title> (from TS-1, AC-1) Priority: P0
Preconditions: ...
Test data: <ref to data set>
Steps:
1. <action> -> Expected: <observable result>
2. <action> -> Expected: <observable result>
Postconditions / cleanup: ...
--- HUMAN REVIEW GATE ---
Assumptions / Unconfirmed expected results / "Approve or edit before these go live"
Guardrails
- Never invent an expected result you cannot justify from an AC or the scenario — mark it "expected result to confirm" instead of guessing.
- Do not fabricate concrete data values inline; reference the data set from the data generator.
- Keep steps deterministic and observable — no "verify it works" hand-waving.
- Cases are a draft until a human approves; you do not sign off your own cases.
04 同仓库更多 Skills
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.
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.
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.
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.
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.
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.