Skip to content

487 — should fill all fields and then cancel it, use recovery and assert all data

Description

Verifies the task form's draft-recovery flow: if the user fills every field and cancels, reopening the form must offer to recover the unsaved draft and restore every field exactly as it was entered.

Preconditions

  • Signed-in tenant with a seeded Advanced project, a one-week sprint, and an employee.
  • Currently on the seeded project's Tasks tab. The form is opened from inside a project so Assignee/Reporter/Sprint inputs are visible.

Steps

  1. Click "Add task" and fill in title (random 4-word string), description, assignee (current owner), story points (random 1–20), priority "Highest", and the seeded sprint.
  2. Pick the start date (today − 5 days) and due date (today + 5 days).
  3. Click "Cancel" to close the form without saving.
  4. Click "Add task" again to reopen it → Expected: the "Recover unsaved changes" modal is displayed.
  5. Click "Recover changes".
  6. Inspect every field → Expected: title, description, project (seeded project), status "To do", assignee and reporter (current owner), story points, priority "Highest", sprint, start date (today − 5d), and due date (today + 5d) all match the original draft.
  • Spec: playwright/tests/integration/task.spec.ts (line 315)