Aglet

Prioritize a missing edge case in regression testing

Rare inputs can have high consequence when they occur at account, payment, data, or release boundaries. Prioritize the case by impact and reversibility, while making the expected behavior explicit enough for a fair comparison.

Decide where the work belongs

  1. Rank consequence

    Describe lost work, blocked progress, incorrect status, privacy exposure, or confusing recovery for users who reach the edge. Avoid inflating priority from hypothetical harm without a reachable path.

  2. Rank reachability

    Use observed examples, valid state transitions, and workflow entry points to estimate whether the case is reachable. Record unknown reachability as evidence work rather than assuming either common or impossible.

  3. Choose a decision point

    Set a review after reproducing the case, clarifying expected behavior, or comparing adjacent inputs. Name the evidence that would raise priority and the condition that allows a planned follow-up.

What to carry forward

The queue decision should include consequence, reachability, expected behavior, owner, and review point. Keep priority high when the case is reachable and hard to recover from; lower it only with evidence of bounded, reversible impact. Rank the gap by task consequence and reachable input frequency, giving precedence to valid inputs that block completion or corrupt interpretation over rare cosmetic differences.

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