

Spur's Functional Testing agent opened Murad's shop-all page, chose "Price, Low to High" from the sort dropdown, and checked that products reloaded correctly. The grid loaded and the sort label updated, but the prices were out of order.

Sort accuracy
Products reordering by the price customers actually pay.
Sale price handling
Discounted items slotting into the correct position in a price-sorted grid.
Filter logic
The sort function reading current sale prices.
Browse experience
Shoppers seeing a genuinely ascending price order when asked.
The customer's live site,
captured by
Spur
during the run.
Before
After
Validate that the first several product prices are in ascending order (lowest first)


5hrs
Dev time saved
Shipped, this one is subtle enough that it takes a focused investigation, someone has to work out whether the sort is pulling from the wrong price field, confirm it only affects sale items, and test the fix.
Misleading
User experience
A shopper sorting by price lowest first is trying to find the best deal. Showing them a $15 item before a $14.40 one because the cheaper item used to cost more quietly undermines the whole experience.
3hrs
Manual QA time
Catching this manually means sorting by price and then reading every product card carefully enough to notice the sequence is off, and knowing enough about the catalogue to spot.
Incorrect price sorting
A 5-step functional test of the sort functionality on Murad's collection page. Spur opened the sort dropdown, selected the price ascending option, waited for the grid to reload, confirmed the sort label updated correctly, then verified the actual product order. Four steps passed, the one that checked the numbers didn't.
Click the SORT BY dropdown
Select [Sort_label:Price, low to high] from the dropdown options
Wait for the product grid to reload
Verify the SORT BY dropdown now shows [Sort_label:Price, low to high] as the current selection
[Sort_label:Price, low to high] the first several product prices are in ascending order (lowest first)