SR-233: Fix WebSocketToastNotifications tests that exercise a component that doesn't exist

[richardiyamura]

Problem

frontend/src/components/__tests__/WebSocketToastNotifications.test.tsx (431 lines, 12 tests) mocks socket.io-client's io() and asserts toast behavior — but there is no WebSocketToastNotifications component anywhere in frontend/src/components/. Every test defines its own local TestComponent inline that wires mockSocket.on('remittance:completed', ...) directly to useToast()/ToastContainer. This suite tests a throwaway scratch harness, not production code — it gives a false signal of coverage for real-time UI updates.

Meanwhile, the actual production real-time status component, frontend/src/components/TransactionStatusTracker.tsx, uses the native WebSocket API, not socket.io-client. Its test file has zero references to WebSocket or socket — it only covers polling and API-fetch paths. The component's actual open/message/error/close event handling, and its malformed-payload catch block, are completely untested.

Suggested approach

1. Either delete/rename WebSocketToastNotifications.test.tsx to reflect that it's testing a generic toast+socket pattern, or wire it to a real component if one is intended to exist.
2. Add tests to TransactionStatusTracker.test.tsx that construct the component with a mocked/fake WebSocket, and assert: status updates on message, graceful handling of malformed JSON payloads, and cleanup (close) on unmount.

[mayasimi]

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

Hello maintainer i can resolve this

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

[alade-dev]

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

Hi, I would like to work on this issue

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

[psamist001]

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

hello maintainer, please feel free to assign this task to me. ETA 8hrs.

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

[drips-wave]

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

🧑‍💻 @psamist001: 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 🌊