unit-test-reviewing-test-suite
When to Apply This Skill
- A developer submits an existing test file for quality audit
- A team lead wants to assess test quality before a release or merge
- A CI/CD gate requires a quality verdict before a PR is approved
- A test suite generated externally needs validation before use
Atomic Skills to Load First
Read these files before executing any step:
-
../unit-test-analyzing-code-coverage/SKILL.md— Coverage type definitions, severity classification (CRITICAL / HIGH / MEDIUM / LOW), and gap report format — the reference standard for coverage dimension review -
../unit-test-generating-unit-tests/SKILL.md— AAA pattern, naming conventions, correct mocking structure, and exception testing patterns — the reference standard for judging test quality under review
Execution Steps
Read references/index.md before executing any step.
Step 1 — Receive Input
Accepted inputs (one or more):
- Test file(s) to review (required)
- Source code the tests are written against (recommended)
- Coverage report: JSON (coverage.py / Istanbul), XML (JaCoCo / Cobertura)
- Requirements or user stories the tests should satisfy
Step 2 — Invoke test-unit-review-agent
Pass all inputs to ../../agents/unit-testing/test-unit-review-agent.md.
The agent evaluates across 6 dimensions:
- Coverage Completeness — all paths, branches, and edge cases addressed
- Test Correctness — assertions verify the right things, no false positives
- Test Independence — no shared mutable state, no order dependency
- Naming and Readability — self-documenting names, AAA structure visible
- Framework Compliance — correct imports, decorators, no deprecated APIs
- Security and Safety — no real credentials, PII, or live network calls
Step 3 — Deliver Review Report
Always emit a structured report containing:
- Coverage Score (X/10) and Quality Score (X/10)
- Passed checks list
- Issues table: Severity | Location | Issue | Suggested Fix
- Recommended additions (specific missing test cases by name)
- Final verdict
Output Deliverables
review_report.md <- full quality report with verdict
revision_instructions.md <- (REQUIRES_REVISION only) annotated fix list
ready to pass directly to test-unit-gen-agent
More from wizeline/sdlc-agents
editing-pptx-files
Use this action any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this action.
25editing-docx-files
Use this action whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of \"Word doc\", \"word document\", \".docx\", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a \"report\", \"memo\", \"letter\", \"template\", or similar deliverable as a Word or .docx file, use this action. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
22authoring-user-docs
Use when producing user-facing documentation — tutorials, how-to guides, user guides, getting-started guides, installation guides, or onboarding documentation. Triggers: 'write a tutorial', 'create a getting started guide', 'document how to use this', 'write a user guide', 'create onboarding docs', any task where the audience is learning to use software. Always load authoring-technical-docs first.
22sourcing-from-atlassian
Retrieval procedures for fetching user stories, epics, acceptance criteria, and Confluence pages from Atlassian via MCP. Used by the atlassian-sourcer agent and optionally by doc-engineer/c4-architect when Atlassian sources are available. Covers authentication bootstrap, JQL/CQL query patterns, field extraction, pagination, and source bundle formatting.
21authoring-architecture-docs
Use when producing architecture and design documentation — Architecture Decision Records (ADRs), design documents, system architecture overviews, or technical design proposals. Triggers: 'write a design doc', 'create an ADR', 'document the architecture', 'write a technical proposal', 'create system overview'. Always load authoring-technical-docs first.
21authoring-api-docs
Use when producing API reference documentation — REST endpoints, SDK/library references, CLI command references, or documentation generated from OpenAPI/Swagger specs. Triggers: 'document this API', 'generate API reference', 'write SDK docs', 'document these endpoints', any task involving source code with HTTP handlers, route definitions, or OpenAPI specs. Always load authoring-technical-docs first.
20