Aglet

Verify document processing statuses across every lifecycle stage

Verification should cover a normal multi-stage document, a failure at an intermediate stage, a slow derivative, and a revisit. Compare status labels and controls with actual availability, ensuring a document is not presented as ready while a required processing result remains absent.

Check whether the outcome improved

  1. Exercise lifecycle outcomes

    Process a document through normal parsing and conversion, then use fixtures that fail or delay a later stage. Record expected status sequence, visible labels, available actions, and derivative availability at each boundary.

  2. Compare status with use

    Try preview, text, download, and downstream submission as each state appears. Verify controls match the required derivative and that pending or failed states cannot be mistaken for ready merely because transfer completed.

  3. Check revisit consistency

    Leave and return during processing and after each outcome. Confirm the same document identity and status sequence remain visible, with a useful recovery action for a failed stage and no skipped transition on reload.

What to carry forward

Accept status behavior when every tested stage and outcome has an accurate label, appropriate action, and stable revisit state. Fail when a required transition disappears, a failure looks pending, or readiness appears before the document capability it represents exists.

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