Aglet

How to verify an understandable import workflow

Verification should show that a person can understand what an import will do before confirming it and can tell what happened afterward. Use small deterministic fixtures and test failure states as carefully as success. Leave unsupported source or provider behavior marked separately from application-controlled proof.

Check whether the outcome improved

  1. Verify the preview

    Select a supported synthetic fixture and assert accepted fields, destination mapping, normalization, required values, and row count are visible before confirmation. Check that labels match the saved result and that secrets or personal data are not echoed into evidence.

  2. Verify failure outcomes

    Submit missing fields, invalid values, duplicate rows, empty input, and mixed-validity fixtures where supported. Assert row-level messages, saved-record counts, and final status are explicit. Confirm a blocked input does not look like a completed import or an invisible partial save.

  3. Verify recovery and access

    Refresh the result, retry an interrupted case, and revisit the import entry point as supported roles permit. Assert mapping and context remain correct, actions are keyboard reachable, and narrow screens expose the full decision and result without clipped controls.

What to carry forward

Accept when supported inputs show an accurate preview, failures reveal durable outcome, and recovery states do not invite unsafe assumptions. Mark unsupported sources and uncontrolled persistence boundaries partial; a polished form alone does not prove import correctness.

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