Our CoreStory + GitHub Copilot Test Generation Playbook works perfectly with GitHub Copilot in VS Code! This supplement covers the setup and workflow differences. All prompting guidance, templates, and strategies from the main playbook apply identically.

Why GitHub Copilot in VS Code for Test Generation?

GitHub Copilot in VS Code offers several advantages for test generation:

• ✅ Direct filesystem writes - Tests written directly to your project, no downloads
• ✅ Immediate test execution - Run tests instantly after generation with VS Code testing tools
• ✅ TDD workflow - Seamless cycle: generate tests → run → fix → iterate
• ✅ Already in your codebase - Full project context from the start
• ✅ CI/CD integration - Easy to script and automate
• ✅ Terminal integration - All your dev tools at hand
• ✅ Agent mode - Autonomous multi-step test generation with automatic framework setup

The Cross-Reference Advantage

Unlike GitHub.com or basic Copilot Chat, VS Code with CoreStory MCP can access both:

• CoreStory’s architectural knowledge: Business rules, specs, design patterns
• Your actual source code: Implementation details, edge cases, real behavior

This enables Copilot to cross-reference — comparing what code should do (from specs) with what it actually does (from source). The result:

• Richer test coverage: Test specified behavior AND actual implementation
• Catch spec drift: Identify when docs and code diverge
• Find hidden features: Discover undocumented functionality that needs tests
• Better alignment: Ensure tests match reality, not outdated specs