unit-test-generating-test-suite
When to Apply This Skill
- A developer provides source code and asks for unit tests
- A CI/CD pipeline triggers test generation for a new commit or PR
- A team wants to bootstrap tests for an untested module
- Any input (code, spec, requirement) needs to produce a runnable test file
Atomic Skills to Load First
Read these files before executing any step — they contain the detailed instructions this orchestration skill depends on:
-
../unit-test-generating-unit-tests/SKILL.md— Test matrix methodology, AAA pattern, mocking, parametrization, exception testing, and framework-specific code examples -
../unit-test-analyzing-code-coverage/SKILL.md— Coverage type definitions and gap report format, used when producing coverage_plan.md at the end of generation
Execution Steps
Read references/index.md before executing any step.
Step 1 — Classify Input
Identify what has been provided and how to interpret it:
source_code → extract signatures, logic paths, side effects requirements → extract acceptance criteria and business rules openapi_spec → extract endpoints, parameters, response schemas mixed → combine all of the above
Also identify: target language, test framework (or auto-detect), scope (function | class | module).
Step 2 — Invoke test-unit-gen-agent
Hand off to ../../agents/unit-testing/test-unit-gen-agent.md with the classified input.
The agent will:
- Build the test case matrix (following unit-test-generating-unit-tests skill)
- Author all test cases using AAA pattern
- Assemble the test file and coverage_plan.md
Step 3 — Invoke test-unit-review-agent
Hand off the generated suite to ../../agents/unit-testing/test-unit-review-agent.md.
The agent returns one of three verdicts: APPROVED → proceed to delivery APPROVED_WITH_NOTES → proceed to delivery with report attached REQUIRES_REVISION → return to Step 2 with annotated fix list
Maximum revision cycles: 2. If still REQUIRES_REVISION after 2 cycles, deliver with full issue report for human resolution.
Output Deliverables
test_<module>.<ext> <- runnable test suite (pytest, Jest, JUnit 5, xUnit, etc.)
coverage_plan.md <- coverage intent summary and gap notes
review_report.md <- quality verdict and any reviewer notes
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