Summary
The transaction history endpoint should always return entries newest-first regardless of the order they were inserted. An integration test should insert transactions out of chronological order and confirm the endpoint consistently returns them sorted descending by timestamp.
Scope
- Insert three transactions with timestamps: T+30s, T+10s, T+20s (intentionally out of order)
- Call the transaction history endpoint
- Assert the response order is T+30s, T+20s, T+10s
- Paginate to the second page and assert the sort order is maintained across pages
- Assert the
created_at field in each entry matches the inserted timestamp
Acceptance Criteria
ETA: 12 hours
Coordinate on Telegram
Summary
The transaction history endpoint should always return entries newest-first regardless of the order they were inserted. An integration test should insert transactions out of chronological order and confirm the endpoint consistently returns them sorted descending by timestamp.
Scope
created_atfield in each entry matches the inserted timestampAcceptance Criteria
created_atin each entry matches the database timestampETA: 12 hours
Coordinate on Telegram