Aglet

Verify a fix for a missing edge case in regression tests

Verification should prove the unusual case works as intended while preserving adjacent behavior. Reuse the original sequence and compare boundary inputs, errors, persistence, and rendered state. Keep expected behavior explicit in the result.

Check whether the outcome improved

  1. Replay the original case

    Use the same input structure, preceding state, role, environment, and action order from triage. Record any changed condition and explain why the comparison remains valid or less certain.

  2. Check neighboring cases

    Exercise nearby minimum, maximum, empty, repeated, and ordinary inputs to catch an overbroad correction. Review stored state, response, visible copy, and recovery after refresh or retry.

  3. Review user outcome

    Confirm the expected result is clear and reversible where appropriate, then apply the evidence rule. If a requirement remains undecided, report behavior verified against the chosen expectation and leave the decision open.

What to carry forward

Verification should state edge case fixed, partially covered, regression found, or expectation unresolved. Close only when the original boundary and adjacent ordinary behavior are both represented in evidence. Exercise the missing case beside lower, equal, and higher neighboring values, then verify the result, error, and recovery path at both ordinary and extreme but valid inputs.

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