coulomb/markitect-main
2
0
Fork 0
Code Issues 60 Pull Requests Actions Projects 12 Releases 1 Wiki Activity

refactor: Make tddai framework project-agnostic and fix test configuration

Browse Source 
FRAMEWORK DECOUPLING:
- Remove all MarkiTect-specific references from tddai core modules
- Update tddai-assistant.md to use generic examples and language
- Change CLI output from "MarkiTect Issues" to "Project Issues"
- Update coverage_analyzer.py docstring to be project-neutral

CONFIGURATION SYSTEM:
- Make tddai configuration flexible via environment variables
- Add comprehensive documentation for project setup in config.py
- Create .env.tddai and tddai-setup.sh for MarkiTect-specific config
- Support configurable workspace naming (.tddai_workspace default)

TEST INFRASTRUCTURE CLEANUP:
- Fix IssueWriter test failures caused by config validation changes
- Implement _get_test_config() helper for isolated test configurations
- Ensure all 13 IssueWriter tests pass with proper test patterns
- Maintain clean test separation and project independence

FRAMEWORK PORTABILITY:
- TDD8 methodology now completely generic and reusable
- Configuration examples for GitHub/GitLab integration
- Ready for extraction to separate repository when needed
- All 45 tests pass cleanly confirming successful refactoring

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2025-09-24 00:04:54 +02:00
parent ef81266eb1
commit 0053fa68ec
8 changed files with 134 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
ProjectDiary.md
View File

@@ -4,6 +4,25 @@ This diary tracks major work packages, events, and milestones in the MarkiTect p
---
## 2025-09-24: TDDAi Framework Decoupling & Project-Agnostic Refactoring
**Progress:** Decoupled tddai framework from MarkiTect-specific implementation and achieved clean test separation
**Contributors:** User (bernd.worsch), Claude Code (Sonnet 4)
**Time Estimate:** ~1-2 hours of refactoring and test cleanup
**AI Resources:** ~15-20 Claude Sonnet 4 conversations, estimated 30K+ tokens
**FRAMEWORK MATURITY:** Successfully transformed tddai from a MarkiTect-specific tool into a truly project-agnostic Test-Driven Development framework. Removed all MarkiTect-specific references from core tddai modules (`coverage_analyzer.py`, `config.py`, `tddai_cli.py`) and updated the tddai-assistant agent definition to use generic examples applicable to any software project. The framework now uses configurable environment variables (`TDDAI_WORKSPACE_DIR`, `TDDAI_GITEA_URL`, `TDDAI_REPO_OWNER`, `TDDAI_REPO_NAME`) allowing deployment across different projects and platforms.
**CONFIGURATION SYSTEM:** Implemented flexible project configuration system that defaults to sensible generic values while supporting per-project customization. Created `.env.tddai` and `tddai-setup.sh` for MarkiTect-specific configuration, demonstrating how any project can configure tddai for their needs. The configuration system validates required fields while maintaining clean separation between framework defaults and project-specific settings.
**TEST INFRASTRUCTURE CLEANUP:** Resolved critical test failures caused by configuration validation after making framework project-agnostic. The IssueWriter tests were failing because they relied on global configuration which now requires project-specific values. Fixed by implementing proper test configuration patterns with `_get_test_config()` helper method, ensuring all 13 IssueWriter tests pass with isolated test configurations. This demonstrates proper testing patterns for project-agnostic frameworks.
**FRAMEWORK PORTABILITY:** The tddai framework is now ready for extraction and reuse in other projects. The TDD8 methodology (ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH) is completely generic and applicable to any software development context. Created comprehensive documentation in `config.py` explaining how to configure tddai for different projects, including examples for GitHub integration and custom workspace naming.
**INFRASTRUCTURE VALIDATION:** All 45 tests pass cleanly, confirming that the refactoring maintained full functionality while achieving project independence. The MarkiTect project continues to use tddai seamlessly through proper environment configuration, demonstrating that the framework decoupling was successful without breaking existing workflows.
---
## 2025-09-23: IssueWriter Implementation & TDD8 Framework Development
**Progress:** Implemented comprehensive IssueWriter for Gitea API updates and formalized TDD8 workflow methodology