Skip to content

Add integration test for the transaction history endpoint returning entries in descending timestamp order #683

Description

@Chucks1093

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

  • Transactions returned newest-first regardless of insertion order
  • Sort order maintained across paginated pages
  • created_at in each entry matches the database timestamp
  • Test fails if the ORDER BY clause is removed

ETA: 12 hours


Coordinate on Telegram

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave program

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions