Check whether the outcome improved
Check a related group
Review events for one resource and confirm group label, summary, order, child identity, and actions remain clear. Open a child and return. Record whether the summary tells enough of the story without repeating every detail.
Check a near match
Use events that share an actor or time but belong to different resources. Confirm they remain separate or visibly scoped. Test an update that changes state so the latest action does not hide an earlier decision.
Review group boundaries
Inspect empty, late-arriving, narrow, and direct destination paths. State tested resource types and omitted platform grouping behavior. Leave a partial pass when child action or summary behavior is not directly observable.
What to carry forward
Verification passes when resource-related events group predictably, near matches stay distinct, and child actions and destinations remain understandable. If one device or resource type is untested, document it. A compact group is not a pass if the summary hides the action a person needs.
Technical background: Android developer documentation.
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