AGENT SKILL

heal-tests

WAY 16 — repair tests broken by UI changes (renamed buttons, moved elements) from the latest run. Use when the user says "heal it", "heal tests", "fix selectors", "tests broke after the redesign".

License 许可
MIT
最近更新
2026-11-06
Stars
★ 5
Forks
4

01 前言 Front Matter

name
heal-tests
description
WAY 16 — repair tests broken by UI changes (renamed buttons, moved elements) from the latest run. Use when the user says "heal it", "heal tests", "fix selectors", "tests broke after the redesign".

03 SKILL.md 正文

WAY 16 — Heal Tests

test-healer also runs automatically inside e2e-session, verify-fix and mr-impact. This WAY is the standalone entry point.

Phase 1: Find locator failures

Take the run the user names, or the newest qa-artifacts/runs/*/results.json. Collect failed scenarios whose error is a locator failure: waiting for getBy…, locator.<action>: Timeout, strict mode violation. For each, keep the error-context attachment path (runs/<id>/artifacts/<test-dir>/error-context.md).

If there's no recent run, offer to run test-execution-agent first.

Phase 2: Propose

Run test-healer in propose mode with all of them in one call. Show a table: test · old locator → candidate · verdict · product_note · files affected (including also_affects for shared steps).

Phase 3: Apply (with the user's approval)

Run test-healer in apply mode for the approved tests only. Report healed / healed-partially / heal-failed.

  • not-healable: element missing → offer report it (WAY 3) with the scenario's steps
  • Every product_note is something the product team should confirm. List them at the end

Save ./qa-artifacts/sessions/heal-<YYYY-MM-DD-HH-MM>.md with the watermark footer.

04 同仓库更多 Skills

GhassenAZZOUZ
GhassenAZZOUZ/claude-qa-agent

write-tests

WAY 4 — write test cases only, no execution. Use when the user says "write it", "write tests", "generate test cases" — an approved test plan (`Plan:`), or requirements (text or a tracker issue) planned and approved first, optional App/Spec/MR or PR → exactly the planned test files.

★ 5
GhassenAZZOUZ
GhassenAZZOUZ/claude-qa-agent

verify-fix

WAY 9 — verify that a bug is fixed by running its regression test. Use when the user says "verify it", "verify fix", "is #142 fixed", "check the fix" with one or more bug refs (#142, SHOP-142), or "verify all" for every open bug that has a regression test.

★ 5
GhassenAZZOUZ
GhassenAZZOUZ/claude-qa-agent

user-story-format

Reference only — the single definition of this project's user-story body (story, Gherkin ACs, Missing Information, DoD) and its AC/scenario rules. Read by user-story-enhancer (WAY 6) and benchmark-gap-story-writer (WAY 8) so stories they write stay identical in shape and WAY 6 can re-score WAY 8's output. Not a workflow on its own.

★ 5
GhassenAZZOUZ
GhassenAZZOUZ/claude-qa-agent

tracker

Provider-neutral contract for every issue-tracker and code-host action (create/update/comment/close issues, attach files, comment on MRs/PRs, read CI runs and logs) plus label conventions and failure handling. Every WAY calls these operations; the matching provider-* skill says how to perform them on GitLab, GitHub, Jira, Azure DevOps, or Bitbucket.

★ 5
GhassenAZZOUZ
GhassenAZZOUZ/claude-qa-agent

traceability

WAY 14 — requirements traceability matrix for a user story (each acceptance criterion) or a test folder written from plain text (each R-NN requirement) → the tests covering it → their latest result → open bugs. Use when the user says "trace it", "traceability", "is #148 covered", "coverage of SHOP-148", "trace it <folder>".

★ 5
GhassenAZZOUZ
GhassenAZZOUZ/claude-qa-agent

test-plan

WAY 19 — design a test plan before any test code. Use when the user says "plan it", "plan tests", "test plan", "design tests" with requirements (text or a tracker issue), optional App/Spec/MR or PR. Output is the test plan (scope, levels, one row per Test#<nn> with category, tags, covers, priority, coverage, entry/exit criteria, risks), reviewed by `review-plan` (WAY 20), filed for approval; `write it Plan:` / `e2e it Plan:` then write exactly that plan. Also holds the plan format every other WAY reads.

★ 5