b2b-backend-create-dev-test-docs

To generate developer test case documents, provide the API endpoint, document path, and optional PRD path. The Skill analyzes Controller and Service code to extract function names, test purposes, and applicable scenarios for your Must Pass tests.

Yes, you can use PRD references to create Must Pass tests. The Skill optionally reads the provided PRD to identify included features, excluded items, and DB-driven validation rules, ensuring your test cases satisfy the documented requirements.

Database validation works by integrating with your dev DB environment to validate sample data. This ensures the generated test case documents contain realistic scenarios and accurate DB-driven validation rules extracted from the provided database environment.

To start automating test case generation, you need the document path, API endpoint, and DB environment. Providing an optional PRD path enhances the output by mapping extracted Controller and Service functions to specific requirement scenarios.

Yes, the generated test case document explicitly includes excluded items and feature scope. By analyzing your codebase and optional PRD references, it defines the exact test purpose, scope, and applicable scenarios to ensure comprehensive developer and QA handoff.

The best way to structure developer test cases for QA handoff is to auto-generate a ready-to-use Markdown document. This document details function names, test purposes, scope, and DB validation rules extracted directly from your Controller and Service code.