---
title: "Verify catalog price sorting stays correct across pagination"
description: "Sort a controlled catalog by price and traverse its result pages, checking global order, variant price policy, ties, and complete product coverage."
canonical_url: "https://vostride.com/agent-library/product-catalog/price-sort-full-results.md"
md_url: "https://vostride.com/agent-library/product-catalog/price-sort-full-results.md"
content_kind: "recipe"
topic: "product-catalog"
---

# Verify catalog price sorting stays correct across pagination

Sort a controlled catalog by price and traverse its result pages, checking global order, variant price policy, ties, and complete product coverage.

## Risk

A list can be sorted correctly within each page while the overall result set remains out of order. The displayed price basis also matters when products have variants, ranges, or active promotions.

## Fixtures

- A fixture catalog large enough to span multiple result pages with deliberately shuffled prices.
- A documented sort price basis and tie-breaking rule, including variant or sale-price treatment.
- An independent ordered list of stable product identifiers and expected displayed price values.

## Steps

1. Open the fixture catalog and select ascending price sort; verify the control and URL state reflect that choice.
2. Compare the first page product identifiers and displayed prices with the expected prefix of the independent ordered list.
3. Continue through every fixture result page and verify ordering across page boundaries, including equal-price ties under the documented rule.
4. Verify the combined identifiers contain every expected product once with no duplicate or missing entries.
5. Switch to descending price and verify the first and final page boundaries follow the documented reversed ordering or tie policy.

## Expected results

- Price ordering is correct across the whole paginated result set.
- Each product appears once and uses the documented price basis.
- Changing sort direction produces the expected new ordering rather than reusing stale page data.

## False-pass traps

- Checking only the first page misses sorting applied after pagination.
- A product minimum variant price and its selected variant price may differ, so the expected basis must be explicit.

## Cleanup

- Remove the fixture catalog records and clear saved sort preferences if the test account stores them.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa auth state](/docs/agent-qa/guides/auth-state.md)

- [Product catalog QA recipes](/agent-library/product-catalog.md)
- [Software factory QA library](/agent-library.md)