# Test search, filters and sorting without hard-coding the data

> Search boxes with suggestions, long lists, sorting and direct links are where list pages break. A plain-language test types, picks, scrolls, deletes and reads the result.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/test-search-filters-and-sorting/

## The pages customers live on

Most of a product is lists: projects, orders, contacts, invoices. They break in specific ways. Suggestions appear and the click lands on the wrong one. The list virtualises, so item 75 does not exist in the page until you scroll. A delete updates the count but the row comes back on refresh. A link straight to an item works from the list and fails when pasted into a new tab.

Scripted tests find these painful because the data moves. A test that clicks "the third row" breaks when the order changes.

## The test

On our practice site:

```text
Open Search, type syd and open Sydney Harbour Bridge from the
suggestions. Verify it shows Place: Sydney Harbour Bridge. Then open
List. Scroll to Item 75, open it and verify the details say You opened
Item 75, then go back. Delete Item 3, then refresh the list. Verify
the header shows Rows: 99, Deleted: Item 3 and Refreshed: 1. Finally
go to /qa/item/42 and verify the page shows You opened Item 42.
```

Every target is named by what is on the screen: the suggestion "Sydney Harbour Bridge", the row "Item 75". The tester scrolls until it finds it.

## What happened

The picture at the top of this page shows two screens from the run: the suggestions for "syd", and the list header after the delete and refresh reading "Rows: 99 · Deleted: Item 3 · Refreshed: 1".

All 11 checks passed in 1 minute 17 seconds, in Chrome on a 1280 × 800 screen. The check for the delete records that the tester clicked the button named "Delete Item 3", that the row disappeared, and that the header changed.

[Recording: The review video of the run.](https://testsy.dev/blog/video/web-search.mp4)

Open [the run](https://app.testsy.dev/share/Gwk9HFsUopC7X_EAqvxEMRR_X2eQNnhh) to step through it. It stays live until 18 February 2027.

## Write it for your app

```text
Sign in with the stored account "customer".
Open Orders, filter by status "Paid" and sort by Total from highest
to lowest.
Check every visible row's status reads Paid and the first row's total
is the largest on the page.
Record the first row's order number.
Open that order and check its detail page shows the same number and
total.
```

```text
Search contacts for "zzz-no-such-name" and check the page says no
contacts were found, instead of showing an empty table or an error.
```

The "record" line asks the tester to read a value without judging it; it appears under **Values seen**, so you know which order the run looked at.

## Cases worth adding

- **Empty results**, as above.
- **Pagination**: page 2 shows different rows from page 1.
- **Filters that survive a reload** or a shared link.
- **Search with special characters**: an apostrophe in a name.

This post is part of [Release testing for product teams](https://testsy.dev/blog/release-testing-for-product-teams/).
