## Major Integration
- ✅ Integrated Requirements Engineering Agent into development workflow
- ✅ Enhanced Makefile with requirements validation targets
- ✅ Added pre-commit validation with mock compatibility checking
- ✅ Enhanced TDD workflow to include foundation analysis
## Test Fixes
- ✅ Fixed GiteaPlugin missing _add_comment_async method
- ✅ Fixed LocalPlugin config.yml file not found errors in tests
- ✅ Enhanced mock objects in CLI tests with proper domain model attributes
- ✅ All Issue #59 tests now passing (38/38 tests pass)
## New Capabilities
- `make validate-requirements` - Foundation analysis before development
- `make check-interface-compatibility INTERFACE=Name` - Interface compatibility checking
- `make generate-dev-checklist FEATURE='Name'` - Development checklist generation
- `make validate-mocks` - Mock object compatibility validation
- `make pre-commit-validate` - Complete pre-commit validation workflow
## Problem Prevention
This integration prevents the exact interface compatibility issues and mock object
mismatches that caused hours of debugging in Issue #59. The Requirements Engineering
Agent provides proactive foundation analysis and catches problems before they occur.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Add comprehensive test runner efficiency improvements to solve pytest issues
and accelerate TDD red-green cycles with intelligent test selection.
Key Improvements:
- Fast TDD test suite (`make test-tdd`) completes in ~17s vs previous timeouts
- Clean test discovery excludes .markitect_workspace directories
- Cache management with `make test-cache-clean` utility
- Intelligent test selection with `make test-changed` for affected files
- Module-specific testing with `make test-module MODULE=name`
- Enhanced test commands with workspace exclusion by default
Performance Results:
- Reduced TDD test feedback time by >60% (17s vs previous timeouts)
- Eliminated "mysterious pytest messages" from stale workspace tests
- Cleaned test cache from 75 failed tests to 3 legitimate failures
- Deselects 92 slow/integration tests during TDD workflows
Technical Implementation:
- Enhanced Makefile with 6 new test efficiency targets
- Updated pytest.ini with norecursedirs to exclude workspace directories
- Comprehensive test suite with 12 test cases covering all functionality
- Integration with existing TDD8 workflow methodology
New Make Targets:
- test-clean: Clean test run (exclude workspaces, fresh cache)
- test-tdd: Quick TDD tests for fast feedback (<30s)
- test-changed: Run tests for changed files only
- test-module: Run tests for specific module
- test-cache-clean: Clean pytest cache
- test-efficient: Enhanced test suite (exclude workspaces)
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
🔧 Schema Management System:
- schema-ingest: Store JSON schema files in database with metadata parsing
- schema-list: List all stored schemas with --format and --names-only options
- schema-get: Retrieve stored schemas to stdout or file
- schema-delete: Remove schemas with confirmation prompts
- Full database integration with schemas table
📊 Enhanced Format Control:
- MARKITECT_DEFAULT_FORMAT environment variable for global format defaults
- Consistent --format options across all CLI commands (table|json|yaml|simple)
- get_default_format() function with fallback logic for invalid values
- Applied format control to query, schema, metadata, list, and ast-stats commands
🛠️ Bug Fixes:
- Fixed ast-stats command empty output by adding 'simple' format handler
- Created missing schema_summary.py for schema visualization tests
- All 394 tests now passing
✨ Usability Improvements:
- Unified format handling across the entire CLI interface
- Environment-based configuration for user preferences
- Enhanced schema management workflow with comprehensive CRUD operations
🧪 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Major Features:
- Implement comprehensive validation error reporting system (Issue #8)
- Add direct CLI access with 'markitect' command
- Create extensive makefile targets for CLI usage
- Enhance schema validation with detailed error collection
Components Added:
- markitect/validation_error.py: ValidationError system with 8 error types
- Enhanced markitect/schema_validator.py: Detailed error reporting methods
- markitect/cli.py: Enhanced with --detailed-errors and --error-format options
- visualize_schema.py: Schema visualization with ASCII and colorful modes
- Comprehensive test suite for validation error reporting
CLI Enhancements:
- Direct 'markitect' command access for all operations
- Makefile targets for typical CLI usage (cli-help, cli-ingest, etc.)
- Support for text, JSON, and markdown error output formats
- Backward compatibility with existing validation functionality
Testing:
- 11 comprehensive tests for Issue #8 validation error reporting
- Tests for schema validation, visualization, and CLI integration
- 100% test coverage for validation error scenarios
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
ARCHITECTURAL MILESTONE: Complete transformation of test suite from issue-based to sophisticated
architectural layer organization with 348 tests across 7 layers (Foundation → Infrastructure →
Integration → Domain → Service → Application → Presentation).
Major Components:
🏗️ ARCHITECTURAL TEST ORGANIZATION:
• Renamed 23 test files to architectural layers (e.g. test_parser.py → test_l7_foundation_markdown_parsing.py)
• Created reverse dependency execution order for 60-80% faster feedback
• Foundation layer (10 tests, ~9s) provides immediate failure detection
• Complete dependency mapping across all 7 architectural layers
🎯 ADVANCED TEST RUNNERS:
• run_architectural_tests.py - Reverse dependency execution with performance metrics
• run_randomized_tests.py - Seed-based randomization for dependency detection
• Comprehensive error handling and colored output for optimal UX
• Support for layer-specific execution and early termination on failures
📋 COMPREHENSIVE DOCUMENTATION:
• ARCHITECTURE.md - 7-layer architecture blueprint with migration strategy
• CAPABILITIES.md - Complete inventory of 73+ system capabilities across 15 categories
• TEST_ARCHITECTURE.md - Detailed test execution strategy and naming conventions
• ARCHITECTURAL_CHAOS_TESTING_ISSUE.md - Chaos engineering gameplan (Issue #35)
🔧 MAKEFILE INTEGRATION:
• 15+ new testing targets (test-arch, test-foundation, test-random, etc.)
• Layer-specific execution (test-infrastructure, test-domain, test-service)
• Advanced options (test-quick, test-layers, test-random-repeat)
• Comprehensive help system with organized testing categories
🎲 RANDOMIZED TESTING:
• Seed-based reproducible test execution for debugging
• Multi-iteration testing to detect flaky tests and hidden dependencies
• Enhanced randomization support with pytest-randomly integration
• Performance analysis across different execution orders
🚀 PERFORMANCE OPTIMIZATION:
• Foundation-first execution prevents cascade failure debugging
• Quick testing (foundation + infrastructure) completes in ~22 seconds
• Layer isolation enables targeted debugging and development
• Optimal feedback loops for architectural development
This revolutionary testing infrastructure establishes MarkiTect as having enterprise-grade
test organization with architectural principles, performance optimization, and advanced
testing methodologies including chaos engineering foundations.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add issue-index command with TSV, CSV, JSON, and fields output formats
- Support sorting by number, title, priority, state, created, updated
- Add filtering by state (open/closed) and priority level
- Include proper data cleaning for Unix pipeline processing
- Add make targets: issues-get, issues-csv, issues-json, issues-high
- Optimize for awk, cut, grep, and other Unix text processing tools
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- 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>
- Add test-new make target for generating test file templates
- Interactive prompt for test name with validation
- Generates structured test class with setup/teardown methods
- Includes basic functionality, edge cases, and error handling placeholders
- Follows TDD best practices with Arrange-Act-Assert pattern
- Auto-generates class names from test names (snake_case to PascalCase)
Usage: make test-new
Then enter test name when prompted (e.g., "schema_validation")
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add test-status make target for fast test status checking
- Shows test file count, cache status, and recent failures
- References detailed test_status_report.md for comprehensive analysis
- Uses pytest cache and filesystem info for speed
- Includes helpful commands for detailed status checking
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Rename "Issue Workspace" category to "TDD Workspace" in help output
- Add tdd- prefix to all workspace-related targets:
- start-issue → tdd-start
- add-test → tdd-add-test
- workspace-status → tdd-status
- finish-issue → tdd-finish
- Update .PHONY declarations for new target names
- Update all CLI output messages to reference new target names
- Maintain backward compatibility in CLI functionality
This provides clearer naming that emphasizes the TDD focus and avoids
confusion with general issue management targets.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Fix test target to run with PYTHONPATH=. for tddai module discovery
- Update all tddai CLI targets to use $(VENV_PYTHON) instead of python3
- Add PYTHONPATH=. to all CLI commands for proper module resolution
- Ensure all targets depend on $(VENV)/bin/activate
Resolves issue where 'make test' was failing due to module import errors.
All 20 tests now pass successfully.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Create comprehensive tddai package with workspace, issue fetcher, and test generator modules
- Add Python CLI interface (tddai_cli.py) to replace complex Makefile shell logic
- Update Makefile targets to use Python CLI for better maintainability
- Implement proper behavior-based tests instead of file existence checks
- Add workspace lifecycle management (create, active, finish, cleanup)
- Add issue fetching from Gitea API with error handling
- Add comprehensive test coverage with 19 passing tests
- Support environment variable configuration for different deployments
This addresses issue #11: Setup TDD workspace infrastructure
All tests pass and the system achieves green state before commit.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add start-issue NUM=X target to create structured issue workspaces
- Add add-test target for iterative test generation within workspace
- Add workspace-status target to monitor active workspace state
- Add finish-issue target to move tests to main and cleanup workspace
- Create workspace structure with requirements.md and test_plan.md templates
- Include .markitect_workspace/ in .gitignore for temporary development files
- Enable multiple test generation per issue with proper organization
- Provide guided workflow for issue breakdown and test planning
This replaces single test generation with comprehensive workspace approach
supporting complex issues requiring multiple test scenarios.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add test-from-issue NUM=X target to generate test skeletons from gitea issues
- Integrate Claude Code requirement checking and issue data fetching
- Provide comprehensive test generation guidance with TDD best practices
- Include issue details, test naming conventions, and pytest requirements
- Enable systematic conversion of issue backlog into test-driven development
- Support error handling for non-existent issues
This establishes the core infrastructure for issue-driven TDD workflow
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add list-issues target for comprehensive issue overview
- Add show-issue NUM=X target for detailed issue inspection
- Add list-open-issues target for active backlog filtering
- Configure gitea API endpoints with proper URL handling
- Include error handling and jq fallback support
- Enable command-line access to issue tracking and backlog
This establishes foundation for issue-driven TDD workflow
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Create ProjectDiary.md with reverse chronological milestone tracking
- Add make add-diary-entry target with Claude Code prerequisite check
- Include initial entry documenting today's infrastructure setup
- Track contributors, time estimates, and AI token usage
- Provide structured format for future development logging
- Guide users through diary entry creation process
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Create comprehensive project status digest documentation
- Add make update-digest target with Claude Code prerequisite check
- Include current architecture, features, and development approach
- Document repository structure and getting started guide
- Add digest update workflow for version releases
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add venv-status target to check current shell activation
- Detect if venv exists but not activated vs actively running
- Handle different venv active vs project venv scenarios
- Use realpath for robust path comparison across symlinks
- Clean output with --no-print-directory flag
- Integrate status check into help target
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
