sorb/ThreadNet-Web
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 4 Wiki Activity

Fix a test that was expecting an edit to be considered unread (#11847)

Browse Source
This commit is contained in:
Andy Balaam
2023-11-11 08:42:02 +00:00
committed by GitHub
parent 722c5ad493
commit 605f4f26ae
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cypress/e2e/read-receipts/editing-messages.spec.ts
+3 -4
View File
@@ -134,8 +134,7 @@ describe("Read receipts", () => {
goTo(room1); goTo(room1);
assertStillRead(room2); assertStillRead(room2);
}); });
// XXX: fails because we see a dot instead of an unread number - probably the server and client disagree it("Editing a message after marking as read makes the room unread", () => {
it.skip("Editing a message after marking as read makes the room unread", () => {
// Given the room is marked as read // Given the room is marked as read
goTo(room1); goTo(room1);
receiveMessages(room2, ["Msg1"]); receiveMessages(room2, ["Msg1"]);
@@ -146,8 +145,8 @@ describe("Read receipts", () => {
// When a message is edited // When a message is edited
receiveMessages(room2, [editOf("Msg1", "Msg1 Edit1")]); receiveMessages(room2, [editOf("Msg1", "Msg1 Edit1")]);
// Then the room becomes unread // Then the room remains unread
assertUnread(room2, 1); assertStillRead(room2);
}); });
it("Editing a reply after reading it makes the room unread", () => { it("Editing a reply after reading it makes the room unread", () => {
// Given the room is all read // Given the room is all read