Check whether the outcome improved
Exercise page boundaries
Test zero, one, exact-page, page-plus-one, and several-page populations with the documented page size. Include records sharing the primary sort value and a final record at the boundary. Assert identifiers, page markers, request parameters, and termination for every sequence.
Assert set coverage
Compare traversed identifiers with the expected filtered set for missing, repeated, extra, and reordered records. Run the same fixture with different page sizes and equivalent filter encodings. A pass requires the set and order contract to hold, not merely a matching total.
Check mutation limits
Verify the documented behavior when records are added, removed, or reordered during traversal, or require a stable snapshot boundary. Confirm a mutable source produces a visible limitation rather than false completeness. Retain request logs and expected sets with the tested revision.
What to carry forward
Accept pagination when every intended identifier appears once, ordering and filters remain stable, page boundaries advance correctly, and termination is explicit. Keep verification open for mutable results without a stated snapshot rule. Report page-size, ordering, and source-change limits with the evidence.
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