Aglet

Verify form validation preserves a user draft

Verification should replay the original invalid submission and inspect the returned form before and after recovery actions. Confirm that retention does not mask validation errors or alter values the server rejected intentionally.

Check whether the outcome improved

  1. Replay the invalid draft

    Use the original field shapes, selections, nested rows, long text, role, and form entry path. Confirm the response identifies the invalid field while redisplaying every valid submitted value.

  2. Correct and resubmit

    Change only the invalid value, submit again, and verify the resulting record or clear error. Check that retained context remains attached and no duplicate or default value appears.

  3. Exercise recovery boundaries

    Refresh, navigate back, and repeat the rejection where relevant. Apply the correction checkpoint and mark coverage partial if a browser or nested field path remains untested.

What to carry forward

Verification should state draft preserved, partially preserved, lost, or inconclusive and identify fields covered. Close only when users can correct the rejected input without reconstructing meaningful work. Replay the invalid draft, correct only the rejected value, and resubmit; then refresh and revisit the form to confirm retained context stays associated with the intended record. Confirm the error summary and field focus still guide correction after retained values are restored.

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