Aglet

Verify facet value coverage on representative product searches

Verification should show that a person can find meaningful facet values in the contexts where the catalog promises them. Test source-backed values, absent values, and a narrow query. Check counts and labels alongside visibility so a present value is not treated as useful by default.

Check whether the outcome improved

  1. Check expected values

    Run a broad query and confirm representative source-backed values appear with understandable labels and usable counts. Compare the facet with the product rows that support it. Record a pass only when selecting the value produces the expected narrowing.

  2. Check absent and dynamic cases

    Use a query with no products for one value, a category with a different taxonomy, and a product missing the attribute. Confirm the interface does not show a misleading empty choice or claim that the facet is universal.

  3. Review the evidence claim

    Check responsive rendering, selected state, reset behavior, and any facet limit. List categories, locales, and index versions not covered. Keep the verification partial when coverage is conditional and state the condition in the closure record.

What to carry forward

Verification passes when representative values appear where expected, absent values are handled honestly, and selecting a facet narrows the intended set. If source or scope limits remain, document them with the tested context rather than calling the entire facet complete.

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