Aglet

Verify result sorting and labels across search contexts

Verification should prove that sort controls describe the order people receive and that defaults remain understandable in each search context. Test explicit selection, direct links, and category return. Check order and labels together rather than accepting a matching control alone.

Check whether the outcome improved

  1. Check explicit sorts

    Select each supported sort and compare representative rows with its definition. Confirm URL, selected control, result order, and pagination agree. Record any intentional tie or promotion rule instead of treating every equal position as a failure.

  2. Check defaults and routes

    Open a fresh search, a category page, and a returned filtered URL. Verify default label and order reflect the route’s promise. Ensure a category-specific position rule does not appear as neutral global relevance.

  3. Review exception copy

    Inspect promotion labels, mobile controls, and back navigation. State tested query families and omitted rules in the closure. If one ordering policy remains unexplained, keep the verification partial and name the needed comparison.

What to carry forward

Verification passes when selected and default sorts produce the documented order and labels match their context. If promotion or category exceptions are untested, state that boundary. A correct order with an incorrect label remains a failed user promise.

Technical background: Elastic 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