Check whether the outcome improved
Check the broad query
Run a query with several known values and compare bucket counts with the defined universe. Select one value and confirm the result total and visible rows change as expected. Record the filter state so the comparison is repeatable.
Check edge cases
Use a parent product with variants, a paginated result, and a refreshed or intentionally delayed index. Confirm the count either follows the documented rule or explains its scope. A count that changes after pagination should not silently redefine the facet.
Review user-facing copy
Inspect labels, selected counts, zero values, reset controls, and narrow layout. Ensure the closure record says what was tested and which aggregation cases were omitted. Keep any unresolved stale-data branch open with a named observation.
What to carry forward
Verification passes when bucket counts, result totals, and scope copy agree for representative selections and known edge cases. If a count is conditional on freshness or grouping, document that condition. A partial pass is preferable to a global claim the evidence cannot support.
Technical background: Adobe 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