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
..
__init__.py	feat: Add comprehensive test coverage assessment system	2025-09-23 03:35:20 +02:00
config.py	fix: Python 3.6 compatibility for tests	2025-09-23 01:40:37 +02:00
coverage_analyzer.py	fix: Correct coverage calculation to return 0% for untested issues	2025-09-23 03:48:51 +02:00
exceptions.py	feat: implement tddai Python library for TDD workspace management	2025-09-22 02:04:19 +02:00
issue_fetcher.py	fix: Python 3.6 compatibility for tests	2025-09-23 01:40:37 +02:00
test_generator.py	feat: implement tddai Python library for TDD workspace management	2025-09-22 02:04:19 +02:00
workspace.py	fix: Python 3.6 compatibility for tests	2025-09-23 01:40:37 +02:00