Aglet

Verify preview readiness without blocking file selection

Verification should prove that selection has a stable meaning while preview work proceeds. Test quick and delayed generation, a preview error, replacement, and multiple files. Confirm controls, file identity, and readiness state agree at each point rather than relying on a single fast fixture.

Check whether the outcome improved

  1. Exercise generation paths

    Select small and large fixtures, an orientation-marked image, and a file that produces a preview error. Record visible state immediately, during pending work, and after completion, including whether the selected file remains present.

  2. Check concurrent actions

    Replace a pending file, add another file, remove one, and continue where permitted. Verify each action targets the correct identity, does not apply a late preview to a replacement, and leaves pending work with a clear disposition.

  3. Inspect ready and failure states

    Confirm a ready preview exposes the intended controls and an error exposes a safe next action. Verify a delayed preview cannot appear as an unselected item or silently overwrite a newer selection.

What to carry forward

Accept preview generation when pending, ready, and error states preserve file identity and the documented actions across timing cases. Fail when selection is blocked without a stated reason, a late result attaches to another file, or an error looks like an unfinished wait.

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