AGENT SKILL

regression-suite-selector

Pick a targeted regression subset for a change instead of running the whole suite. Use when an engineer says "what regression should I run for this PR", "pick regression tests", or describes a change and wants the affected tests identified. Maps changed areas to the tests that exercise them, ranks by risk, and proposes a run set with a rationale — plus a safety net of always-run tests. It recommends; a human confirms before anything is skipped.

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

01 前言 Front Matter

name
regression-suite-selector
license
MIT
metadata
{ "author": "TheTestingAcademy", "version": "1.0.0", "stlc-phase": "Test Execution" }
description
Pick a targeted regression subset for a change instead of running the whole suite. Use when an engineer says "what regression should I run for this PR", "pick regression tests", or describes a change and wants the affected tests identified. Maps changed areas to the tests that exercise them, ranks by risk, and proposes a run set with a rationale — plus a safety net of always-run tests. It recommends; a human confirms before anything is skipped.

03 SKILL.md 正文

Regression Suite Selector

You answer "what actually needs re-running for this change?" — trading a full-suite run for a risk-justified subset, while being honest about what the subset leaves uncovered.

When to use

  • A PR or change set needs a focused regression run, not the entire suite.
  • Time or CI budget is tight and you need the highest-value tests for a change.
  • Someone asks which tests a given area touches.

Workflow

  1. Understand the change. Take the diff, changed files/modules, or a description. If the scope is unclear, ask — do not guess which areas moved.
  2. Map impact. Trace changed areas to the features, endpoints, and shared components they affect, including likely downstream/blast-radius effects.
  3. Select tests. Match affected areas to existing tests. Rank Must-run (directly hits the change), Should-run (shared/adjacent), and Skip-with-reason. Always include a smoke/critical safety net regardless of the change.
  4. State the trade-off. Say plainly what the selected set does NOT cover, so the risk of skipping is visible.
  5. HUMAN REVIEW GATE (mandatory). Present the selection as a recommendation. List assumptions about the impact map and what is being skipped. Ask for confirmation before any test is dropped from the run.

Output shape

## Regression Selection — <PR / change>
Changed areas: <modules/files>  ->  Impacted: <features/endpoints>
Must-run:    [ tests directly exercising the change ]
Should-run:  [ shared/adjacent tests ]
Safety net:  [ smoke / critical-path — always ]
Skip (with reason): [ test — why it is unaffected ]
Not covered by this subset: <explicit gap>
--- HUMAN REVIEW GATE ---
Impact assumptions / what is skipped / "Confirm before dropping tests from the run"

Guardrails

  • Never present the subset as risk-free — always name what it does not cover.
  • Do not invent test-to-area mappings; if the link is uncertain, mark it and lean toward including.
  • Always keep a smoke/critical safety net even for a "small" change.
  • The selection is a recommendation; a human owns the decision to skip.

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