Aglet

Verify upload cancellation states after every response ordering

Verification should prove that cancellation has one understandable meaning even when network timing changes. Test a normal stop, an in-flight response, a final-chunk race, and a later page revisit. Confirm the artifact state and next action agree across each surface.

Check whether the outcome improved

  1. Exercise response orderings

    Cancel before a request responds, immediately after an acknowledgment, and while the final range is in flight. Record the expected terminal state for each case and verify that a late response cannot silently turn cancellation into completion.

  2. Inspect artifact visibility

    Revisit the upload list and any detail or retry surface after each case. Confirm retained partial data is labeled and actionable, while discarded data no longer appears as resumable. Check that one file identity is not shown twice.

  3. Check the next action

    Try the documented follow-up: resume, restart, remove, or choose another file. Verify the control is available only for the intended state and that its result preserves the cancellation contract rather than creating an accidental duplicate.

What to carry forward

Accept cancellation when every tested response ordering yields the documented terminal state, a clear artifact disposition, and a correct next action. Fail when a late response changes the meaning without explanation or when a partial artifact cannot be reconciled with the visible item.

Technical background: MDN reference.

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