sadatmalik
commented
2 days ago Testing Plan for Real-Time Chat Reactions
-
[x] 1. Single User Reaction Update
- Scenario: User A adds a reaction to their own post.
- Expected Outcome: Reaction is visible instantly without refreshing the page.
-
[x] 2. Other User Reaction Update (Admin/Admin Portal)
- Scenario: User A posts a message. User B in their admin portal reacts to the post.
- Expected Outcome: User A sees the reaction immediately. No refresh needed.
-
[x] 3. Cross-Portal Reaction Update (Admin/Candidate Portal)
- Scenario: User A in admin portal posts a message. User C in candidate portal reacts to the post.
- Expected Outcome: Both User A and User C see the reaction immediately on their respective portals.
-
[x] 4. Disconnection and Reconnection Handling
- Scenario: User A posts a message and is disconnected from the WebSocket. User B reacts during this time, and then User A reconnects.
- Expected Outcome: Once User A reconnects, they receive the latest reaction without needing to refresh the page manually.
-
[x] 5. Multiple Devices for One User
- Scenario: User A has two devices (browser tabs, mobile app, etc.) connected to the same chat. User B reacts to a post by User A.
- Expected Outcome: Reaction is updated in real-time on both devices.
-
[x] 6. Multiple Users Reacting with Different Reactions
- Scenario: Multiple users react to the same post with different reactions (like, heart, laugh, etc.).
- Expected Outcome: All users see the list of reactions and total count updated instantly without refresh.
-
[x] 7. Multiple Reactions by Same User (Toggling)
- Scenario: User A reacts to a post (like), then changes their mind and removes or changes the reaction.
- Expected Outcome: The reaction is updated/removed in real time for all other users.
-
[ ] 8. Race Condition with Multiple Users Reacting Simultaneously
- Scenario: User A, User B, and User C all react to a post at the same time.
- Expected Outcome: All reactions appear consistently without conflict or any resfresh required.
-
[ ] 9. Mobile vs. Desktop -- test this scenario in staging after merge and deploy
- Scenario: User A on desktop adds a reaction, and User B on mobile sees the post.
- Expected Outcome: Reactions update in real-time across both desktop and mobile platforms.
Testing Accounts
User A = sadat@test.tbb (Admin Source) User B = sadat@test.crs (Admin Source) User C = sadat.malik@test.org (Candidate) User D = sadat@iress.uk (Admin Employer)
Based on feedback that reactions are essentially a specific kind of post update; this issue presents an alternative implementation approach to #1417