Aglet

Verify document processing output remains format-stable

Verification should compare repeated processing of a fixed source and one intentional context change. Inspect output properties that readers or downstream tools rely on, not only file length. Confirm expected changes are documented and unexpected drift is detected before delivery to a consumer.

Check whether the outcome improved

  1. Run repeatability cases

    Process the same marked source twice under unchanged context and once after a documented option or version change. Record expected format, metadata, text, pages, rendering landmarks, and filename for each result.

  2. Check semantic properties

    Compare output format, extension, metadata, page order, searchable text, rendering, and derivative identity. Distinguish acceptable binary or timestamp variation from a change that alters reader capability or downstream compatibility.

  3. Inspect handoff behavior

    Open, download, search, compare, and hand off each output through the intended workflow. Verify labels and controls describe the representation, and that a changed result is either expected and explained or stopped for review.

What to carry forward

Accept format behavior when stable runs preserve contracted capabilities and intentional changes are visible with their context. Fail when output properties drift without explanation, file naming misstates the representation, or downstream use changes unexpectedly in a way reviewers cannot explain.

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