?
TRCKR-167
testing,e2e,playwright
Created: 2025-12-20 Updated: 2025-12-21
Relationships Loading...
Attachments
Loading...
Comments (1)
agent · 2025-12-21
## Implementation Complete Created E2E test for creating an issue with all fields populated. ### What was implemented Created `tests/e2e/test_issue_all_fields.py` with a comprehensive test that: 1. **Sets up test data via API**: - Creates a project (AFT - All Fields Test) - Creates a milestone (Sprint 1) 2. **Fills in all form fields via UI**: - Title: "Complete Issue Test" - Description: Markdown with header and list items - Status: in-progress (via PropertyDropdown) - Priority: high (via PropertyDropdown) - Assignee: test-user (via JavaScript) - Project: selects created project (via PropertyDropdown) - Labels: bug, feature, documentation (via MultiSelectDropdown) - Milestone: Sprint 1 (via MoreMenu submenu) 3. **Verifies via API**: - All fields were correctly persisted - Issue identifier has project prefix (AFT-) - Labels appear in table with correct data-testid ### Technical notes - Added helper function `select_milestone_via_more_menu()` to handle the complex milestone selection UI - Required JavaScript cleanup after milestone selection due to dropdown overlay issue - Reused existing conftest helpers: `add_label_via_multiselect`, `select_property_dropdown_value`, etc. ### Files changed - `tests/e2e/test_issue_all_fields.py` (new file, 276 lines) ### Test verification Test passes reliably (verified 3 consecutive runs at 6-9 seconds each)