An advanced markdown engine
Find a file
tegwick 3e7d2b55d5 fix: Resolve TDD infrastructure test failures and API mismatches
Comprehensive fix for 9 failing TDD tests caused by API mismatches between
test expectations and actual WorkspaceManager implementation.

**Root Cause Analysis:**
- Tests incorrectly passed strings instead of TddaiConfig objects
- API return type mismatches (expected Path, got Workspace objects)
- Missing methods: add_test_to_workspace() and get_workspace_status()
- Incorrect assumptions about WorkspaceStatus enum attributes
- Metadata field name differences (issue_number vs number)

**WorkspaceManager API Fixes:**
- Added add_test_to_workspace(filename, content) method
- Added get_workspace_status() alias for get_status()
- Enhanced error handling for workspace operations

**Test Corrections:**
- Fixed WorkspaceManager initialization to use TddaiConfig objects
- Updated API usage to match Workspace object return types
- Corrected WorkspaceStatus enum handling
- Fixed metadata field expectations
- Updated error message patterns to match actual implementation

**Results:**
- Before: 9 failing tests, 23 passing (28% failure rate)
- After: 0 failing tests, 32 passing (100% success rate)

This restores the TDD infrastructure to full functionality, validating
that our Issue #1 implementation approach was sound and the tooling
is ready for productive development.

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

Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 04:46:22 +02:00
.claude agent: Needed to reinstall claude on Ubuntu 24.04 2025-09-23 01:21:34 +02:00
.venv chore: Updated to Ubuntu 24.04 and created new .venv 2025-09-23 01:19:57 +02:00
.venv_old chore: Keep old venv from ubuntu 18.04 for now just in case. 2025-09-23 01:16:12 +02:00
markitect feat: Implement Issue #1 - Database initialization and front matter parsing 2025-09-23 04:28:29 +02:00
tddai fix: Resolve TDD infrastructure test failures and API mismatches 2025-09-23 04:46:22 +02:00
tests fix: Resolve TDD infrastructure test failures and API mismatches 2025-09-23 04:46:22 +02:00
wiki@32f20201ac Update wiki submodule to latest 2025-09-21 23:24:37 +02:00
.gitignore build: Add issue workspace system for structured TDD workflow 2025-09-22 01:28:55 +02:00
.gitmodules Add wiki as submodule tracking main 2025-09-16 23:28:11 +02:00
install-claude.sh agent: Finally found a way to install claude again 2025-09-23 02:24:09 +02:00
install-depends.sh build: Helpers to initially setup the dev env 2025-09-23 01:23:32 +02:00
install-nvm.sh build: Helpers to initially setup the dev env 2025-09-23 01:23:32 +02:00
install-pip.sh feat: Add Python dependency management and fix test environment 2025-09-23 02:41:32 +02:00
Makefile feat: Add comprehensive test coverage assessment system 2025-09-23 03:35:20 +02:00
NEXT.md chore: Change NEXT file to correct filetype 2025-09-22 21:11:38 +02:00
ProjectDiary.md docs: Add comprehensive digest for test coverage assessment system 2025-09-23 03:52:50 +02:00
ProjectStatusDigest.md docs: Add comprehensive digest for test coverage assessment system 2025-09-23 03:52:50 +02:00
pyproject.toml feat: Implement Issue #1 - Database initialization and front matter parsing 2025-09-23 04:28:29 +02:00
README.md chore: first commit 2025-09-16 02:56:34 +02:00
RelevantClaudeIssues.md docs: Document subagent infrastructure resolution and environment restoration 2025-09-23 02:58:36 +02:00
tddai_cli.py feat: Add comprehensive test coverage assessment system 2025-09-23 03:35:20 +02:00
test_status_report.md feat: Add make test-status for quick test overview without re-running 2025-09-23 03:16:50 +02:00

MarkiTect - Advanced Markdown Engine

Your Markdown, Redefined.

MarkiTect is an open-source tool designed to bring structural integrity and consistency to your Markdown files. It empowers you to stop treating your documentation as plain text and start managing it as structured data.

With MarkiTect, you can define a schema to enforce the exact structure of your documents—ensuring every file has the right sections, headings, and hierarchy. This makes it easier than ever to maintain, validate, and automate large-scale documentation projects. Build with confidence, not with manual checks.