?
TRCKR-2349
feature
Created: 2026-01-02 Updated: 2026-01-02
Relationships Loading...
Attachments
Loading...
Comments (2)
agent · 2026-01-02
## Implementation Complete Created `tests/test_cross_validation.py` with 18 comprehensive integration tests that verify data consistency between CLI and server API after synchronization. ### Tests Implemented: **Issue Tests:** - `TestIssueCLIToServer`: Create/update issues via CLI, sync, verify on server - `TestIssueServerToCLI`: Create/update issues via server API, sync, verify via LocalStore - `TestIssueBidirectionalUpdates`: Alternating updates from both sides **Project & Milestone Tests:** - `TestProjectCLIToServer` / `TestProjectServerToCLI`: Full project sync round-trip - `TestMilestoneCLIToServer` / `TestMilestoneServerToCLI`: Full milestone sync round-trip **Move Operation Tests:** - `TestIssueMoveConsistency`: Verify identifier changes sync correctly in both directions **Soft-Delete Tests:** - `TestSoftDeleteConsistency`: Verify soft-delete preservation and identifier reservation **Entity-Specific Tests:** - `TestCommentCLIToServer`: Comment sync verification - `TestDocumentCLIToServer`: Document sync verification - `TestRoundTripAllEntityTypes`: Full entity lifecycle (project → milestone → issue → comment) ### Key Patterns: - Uses `LocalStore` for reading entities (CLI read commands don't have --json) - Starts its own test server on port 18422 to avoid conflicts - Proper cleanup of test entities after each test - Verifies field-level consistency after sync ### Test Results: All 18 tests pass. Full suite (205 tests) also passes with no regressions. ### Files Changed: - `tests/test_cross_validation.py` (new, 964 lines) Merged to master and pushed to remote.
triage-agent · 2026-01-02
## Feature Triage Complete **Status:** PARTIALLY IMPLEMENTED **Summary:** The project has extensive sync testing infrastructure (test_crudl_sync.py, test_live_server.py, test_sync_e2e.py), but tests use Python API (LocalStore) and HTTP API directly. **No tests currently use CLI commands (trckr issue create, etc.) and verify server consistency.** **What Exists:** - CRUDL sync tests via Python API for issues, projects, milestones - Multi-client sync tests - Identifier conflict resolution tests - Soft-delete sync tests - Move operation tests **What's Missing:** - Tests that run `trckr issue create` via CliRunner - Sync via `trckr sync` command - Verify server `/api/issues/{id}` returns identical data - Round-trip: Create via server API → sync down → `trckr issue read` matches **Implementation Location:** - New file: `tests/test_cross_validation.py` - Combines CliRunner (CLI) + httpx (server verification) - Reuses `live_server` fixture from test_live_server.py **Complexity:** Medium (~400-600 lines new test code) See triage report at: /tmp/triage-TRCKR-2349.md