qfai-atdd

Translate scenario feature files into runnable acceptance test code.

3|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/aganesy/QFAI --skill qfai-atdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qfai-atdd
Source: https://github.com/aganesy/QFAI/tree/main/packages/qfai/assets/init/.qfai/assistant/skills/qfai-atdd
Command: npx skills add https://github.com/aganesy/QFAI --skill qfai-atdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the creation of executable acceptance tests (E2E, API, Integration) based on defined scenarios, ensuring software meets quality and acceptance criteria.

Core Features & Use Cases

  • Automated Test Generation: Translates feature files (.feature) into runnable test code.
  • Coverage Management: Ensures all defined scenarios are implemented and tracked.
  • Traceability: Maintains alignment between requirements, scenarios, and tests.
  • Use Case: After defining user stories and acceptance criteria in scenario.feature files, use this Skill to generate the corresponding API and E2E tests, which can then be run in CI to validate new code.

Quick Start

Use the qfai-atdd skill to implement automated acceptance tests for the spec ID 'spec-XXXX'.

Frequently Asked Questions about qfai-atdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate executable acceptance tests from feature files?

Executable acceptance tests are generated by translating scenario feature files into runnable API, E2E, and integration test code. The process enforces 100% scenario coverage and maintains traceability from requirements to tests.

What is ATDD and how does automated test generation work?

ATDD involves implementing executable acceptance tests by translating defined scenario feature files into runnable code. This ensures software meets acceptance criteria by automating E2E, API, and integration test creation.

How do I ensure full scenario coverage when automating E2E and API tests?

Full scenario coverage for E2E and API tests is enforced by translating all defined scenarios in feature files into runnable code. The workflow tracks every requirement and maintains traceability to validate complete implementation.

Can I use this approach to generate integration tests for CI pipelines?

Yes, you can generate API, integration, and E2E tests from scenario feature files to run in CI pipelines. The generated test code validates new code against defined user stories and acceptance criteria.

Do I need predefined user stories to automate acceptance test creation?

Yes, you need to define user stories and acceptance criteria in scenario.feature files first. The automated test generation translates these predefined scenarios into corresponding runnable test code.

What is the best way to maintain traceability between requirements and automated tests?

Traceability between requirements and automated tests is maintained by translating scenario feature files into runnable code while tracking coverage. This ensures every defined scenario aligns directly with the implemented acceptance tests.