3 Commits

Author	SHA1	Message	Date
tegwick	73185f2c96	fix: Correct coverage calculation to return 0% for untested issues ... Previously, coverage analysis was incorrectly using keywords from all existing tests, causing false positives where untested issues showed coverage percentages instead of 0%. Changes: - Only count tests specifically related to the analyzed issue - Return 0% coverage when no issue-specific tests exist - Maintain accurate coverage calculation for tested issues This ensures that Issue #3 correctly shows 0.0% coverage instead of 33.3%, while Issue #11 still correctly shows 100.0% coverage. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-09-23 03:48:51 +02:00
tegwick	e0b4ab0124	fix: Resolve false positive coverage reporting for untested functionality ... Major improvements to coverage analysis accuracy: **Fixed Coverage Calculation Logic:** - Remove false positive where untested issues showed 100% coverage - Require actual keyword overlap for coverage validation - Treat requirements with no extractable keywords as gaps (not covered) - Changed from assuming coverage if any tests exist to requiring keyword matches **Enhanced Requirement Extraction:** - Add patterns for data operations (read, store, save, load, retrieve, fetch) - Add data handling patterns (file, database, storage, content) - Add format handling patterns (schema, json, markdown, ast) - Intelligent analysis of simple issues with enhanced requirement generation - Title-based requirement extraction for comprehensive coverage **Stricter Coverage Validation:** - Requirements without keywords always considered gaps - No more false positives for completely untested functionality - Improved gap detection for better accuracy **Results:** - Issue #3 now correctly shows 33.3% coverage (was 100% false positive) - Issue #11 still correctly shows 100% coverage (comprehensive tests) - More detailed requirement breakdown for simple issues 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-09-23 03:43:24 +02:00
tegwick	f485b24a5a	feat: Add comprehensive test coverage assessment system ... - Add CoverageAnalyzer class for analyzing functional test coverage against issues - Intelligent requirement extraction from issue descriptions using regex patterns - Automatic coverage gap detection with priority classification (critical/important/nice-to-have) - Smart keyword matching between requirements and existing tests - Comprehensive CLI interface with make test-coverage NUM=X command - Detailed recommendations with specific test suggestions and TDD workflow guidance Features: - Extracts requirements from issue text patterns (user can, must, should, examples, etc.) - Analyzes existing test files and methods for coverage keywords - Calculates coverage percentage based on requirement-to-test matching - Provides specific test name and file suggestions for gaps - Prioritizes recommendations by requirement criticality - Integrates with existing TDD workflow (tdd-start, tdd-add-test) Usage: make test-coverage NUM=5 Example output shows 28.6% coverage for Issue #5 with specific gap recommendations 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-09-23 03:35:20 +02:00