[Test] Component: Transaction History (List View) Empty States

[johdanike]

Verify that a friendly empty state component renders when the user has no cross-border transactions.

This issue tracks the implementation of automated component/E2E tests to ensure UI stability.

Requirements

• Fork the repository and create a new branch using the designated branch name.
• Write the required tests using the project's testing framework (e.g., Jest, React Testing Library, Cypress).
• Mock external dependencies (APIs, Web3 wallets, WebSockets) to prevent flaky tests.
• Ensure the new tests pass reliably and meet code coverage standards.
• Run the full test suite locally to verify no existing tests are broken.

Proposed Actions 🛠️

Fork and Create Branch:

git checkout -b test-comp-tx-history-list

Implement Tests:

• Setup the test file in the appropriate directory.
• Write tests covering the happy path (success states) for this specific component.
• Write tests covering edge cases, empty states, and error handling.

Run Tests and Commit:

git commit -m "Test: Implement Component: Transaction History (List View) Empty States"

Required 📋

Guidelines:

• Assignment: Don't create a pull request if you weren’t assigned to this issue.
• Timeframe: Complete the task within 3 business days.
• PR description must include: Closes #[issue_id]

Thank you for your contribution 🙏

[abdulwahabmonilola-ctrl]

@abdulwahabmonilola-ctrl has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, this task matches my skills and I’m confident I can resolve it properly. Kindly consider assigning it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abdulwahabmonilola-ctrl to this issue.

[deep-bhikadiya]

@deep-bhikadiya has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, this looks like something I can help with. I'd appreciate being assigned to it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @deep-bhikadiya to this issue.

[AdaBliss]

@AdaBliss has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to take this issue on. I’ll review the current implementation and relevant project guidelines first, then implement a maintainable solution with tests covering the expected behavior and edge cases

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AdaBliss to this issue.

[drips-wave]

Congratulations, @AdaBliss! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @AdaBliss: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊