dev-test

You can generate a test plan and stubs from acceptance criteria by running a pre-implementation test planning process that ingests issue data and plan docs. It scaffolds placeholder test files grouped by happy, edge, and error cases before any implementation begins.

Test plan generation uses GitHub CLI to look up issue bodies and extract acceptance criteria directly. It pulls ACs from GitHub issue data and local plan docs, counts the criteria, and writes a structured test plan file scoped to that specific issue.

Yes, automated test scaffolding requires a project .paadhai.json config file on your git branch. This config supplies the stack build and test commands needed to verify that placeholder assertions do not fail before committing the generated test stubs.

Yes, test planning targets feature or fix branches in git repositories before implementation starts. It derives the testing scope from the branch context and linked GitHub issue data, producing a documented test roadmap and placeholder stubs for the upcoming code.

The best way to structure test cases for new features is to group them into happy, edge, and error cases derived directly from acceptance criteria. This approach writes a detailed test plan file and scaffolds matching placeholder test files before implementation begins.

Placeholder test files should not fail the build because the test planning process runs configured build and test commands to verify them. If they fail, check your project .paadhai.json config file to ensure the stack build and test commands are correctly defined for your environment.