Skip to main content
bash TV

Spec-Driven Development with AI: Requirements to Tests to Coverage

TestMu AI (Formerly LambdaTest)

23 views16 Nov 2026

YouTube

In spec-driven development, the spec comes first and everything else, including the tests, comes from it. In this video, I give Kane CLI the spec for an airline's online check-in, and it turns that spec into tests, runs them and reports coverage, all from my terminal. Every test stays linked to the requirement it checks. 👉 Try Kane CLI by TestMu AI: https://www.testmuai.com/kane-cli/?utm_source=youtube&utm_medium=video&utm_term=jpAVmLkmd_M&utm_campaign=spec_driven_development_cli In this video, you'll learn: ✅ What spec-driven development means for testing ✅ Ingesting a requirements spec into Kane CLI ✅ How Kane CLI proposes use cases and avoids duplicates from other sources ✅ Reviewing and approving use cases before anything is trusted ✅ Turning one use case into acceptance criteria and test scenarios ✅ Keeping coverage gaps visible instead of hidden ✅ Running the check-in test and reviewing step-by-step evidence ✅ Requirement coverage: which parts of the spec are proven ✅ Tracing every test back to the spec when requirements change 🛠️ Get started: npm i -g @testmuai/kane-cli, then point kane-cli context ingest at your own spec. 🔗 Tools and docs mentioned: Kane CLI: https://www.testmuai.com/kane-cli/ Spec-Driven Testing with Kane CLI: https://www.testmuai.com/spec-driven-testing/ Kane CLI docs: https://www.testmuai.com/support/docs/kane-cli-introduction/ Read the full guide, What Is Spec-Driven Development: https://www.testmuai.com/blog/spec-driven-development/ Spec-Driven Development From the Command Line: https://www.testmuai.com/blog/spec-driven-development-command-line/ ⏱️ Chapters: 00:00 What is spec-driven development? 00:25 What this video covers 00:40 The spec: numbered requirements 00:55 Ingesting the spec into Kane CLI 01:15 Adding the support FAQ as a second source 01:40 Reviewing and approving use cases 02:05 Designing tests: acceptance criteria 02:20 Picking the scenarios that matter most 02:30 Coverage gaps stay visible 02:55 Approving the test design 03:10 Running the check-in test 03:30 Test passed: every step saved as evidence 03:45 Requirement coverage report 04:10 Mapping the spec to every test 04:35 Recap: the spec as the source of truth 05:00 Try it on your own spec 💬 Can you trace your tests back to your requirements today? Tell us in the comments. #SpecDrivenDevelopment #AITesting #RequirementsTesting #TestAutomation #TestMuAI

Join the discussion

Have something to add?

Sign in to reply, follow this thread, and earn XP when your answer helps someone.