Check whether the outcome improved
Exercise validation outcomes
Upload a valid fixture, a deliberately invalid fixture, and a fixture that follows a longer path. Record the visible state immediately after transfer and at final result, ensuring pending wording does not imply acceptance or rejection.
Check actions at each state
Try preview, submit, replace, retry, and leave-and-return where the workflow supports them. Confirm each control matches the file state, and that a pending item cannot be mistaken for a ready one merely because bytes transferred successfully.
Inspect revisit and failure
Reload or reopen the workflow after each outcome and verify the same validation state and file identity remain clear. Check a validation failure path for useful next action and ensure it does not collapse into a generic transfer error.
What to carry forward
Accept the handoff when every tested outcome exposes a stable validation state, correct controls, and a clear file identity across revisit. Fail when transfer completion implies readiness, rejection is hidden, or a delayed result leaves the user with no safe next action.
Technical background: W3C guidance.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow