kodjo/MyFastHtml
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Working on TreeView. Enhanced matches capabilities

Browse Source
This commit is contained in:
Kodjo Sossouvi
2025-11-27 23:46:06 +01:00
parent a3783b5fb6
commit 3271aa0d61
10 changed files with 1297 additions and 707 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
.claude/commands/unit-tester.md
View File

@@ -15,10 +15,12 @@ Write comprehensive unit tests for existing code by:
### UTR-1: Test Analysis Before Implementation
Before writing any tests:
1. **Analyze the code thoroughly** - Read and understand the implementation
2. **Identify all test scenarios** - List both success and failure cases
3. **Present test plan** - Describe what each test will verify
4. **Wait for validation** - Only proceed after explicit approval
1. **Check for existing tests first** - Look for corresponding test file (e.g., `src/foo/bar.py` → `tests/foo/test_bar.py`)
2. **Analyze the code thoroughly** - Read and understand the implementation
3. **If tests exist**: Identify what's already covered and what's missing
4. **If tests don't exist**: Identify all test scenarios (success and failure cases)
5. **Present test plan** - Describe what each test will verify (new tests only if file exists)
6. **Wait for validation** - Only proceed after explicit approval
### UTR-2: Test Naming Conventions
@@ -200,11 +202,14 @@ class TestControlRender:
### UTR-11: Test Workflow
1. **Receive code to test** - User provides file path or code section
2. **Analyze code** - Read and understand implementation
3. **Propose test plan** - List all tests with brief explanations
4. **Wait for approval** - User validates the test plan
5. **Implement tests** - Write all approved tests
6. **Verify** - Ensure tests follow naming conventions and structure
2. **Check existing tests** - Look for corresponding test file and read it if it exists
3. **Analyze code** - Read and understand implementation
4. **Gap analysis** - If tests exist, identify what's missing; otherwise identify all scenarios
5. **Propose test plan** - List new/missing tests with brief explanations
6. **Wait for approval** - User validates the test plan
7. **Implement tests** - Write all approved tests
8. **Verify** - Ensure tests follow naming conventions and structure
9. **Ask before running** - Do NOT automatically run tests with pytest. Ask user first if they want to run the tests.
## Managing Rules