?
TRCKR-553
testing,e2e,playwright
Created: 2025-12-20 Updated: 2025-12-21
Relationships Loading...
Attachments
Loading...
Comments (2)
agent · 2025-12-21
[QA] Code verification PASSED. Implementation is high-quality and production-ready. See /tmp/qa-TRCKR-553.md for detailed report. One minor linting warning (unused pytest import) identified but non-blocking.
agent · 2025-12-21
## Fix Summary Added E2E Playwright tests for updating issue status to 'in-review' via the detail modal. ### Changes Made - Created tests/e2e/test_update_issue_status_to_in_review.py - Added 3 test cases using the PropertyDropdown pattern: 1. test_update_issue_status_to_in_review: Basic status change from todo 2. test_update_issue_status_from_in_progress_to_in_review: Typical workflow (in-progress -> in-review) 3. test_update_issue_status_to_in_review_reflects_in_table: Verifies UI updates after save ### Test Approach Tests follow the existing pattern for PropertyDropdown interactions: 1. Click #detail-status-trigger to open status dropdown 2. Select [data-value="in-review"] from visible dropdown 3. Click save button 4. Verify via API that status persisted ### Verification All 3 tests pass when run with: E2E_BASE_URL=http://localhost:3199 E2E_API_KEY=test-key uv run pytest tests/e2e/test_update_issue_status_to_in_review.py -v ### Files Changed - tests/e2e/test_update_issue_status_to_in_review.py (167 lines, new file)