From 605f4f26aec1bcea7ece0f8789b7dce5f1cd5c78 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Sat, 11 Nov 2023 08:42:02 +0000 Subject: [PATCH] Fix a test that was expecting an edit to be considered unread (#11847) --- cypress/e2e/read-receipts/editing-messages.spec.ts | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/cypress/e2e/read-receipts/editing-messages.spec.ts b/cypress/e2e/read-receipts/editing-messages.spec.ts index bbaa15d659..04b21acd1a 100644 --- a/cypress/e2e/read-receipts/editing-messages.spec.ts +++ b/cypress/e2e/read-receipts/editing-messages.spec.ts @@ -134,8 +134,7 @@ describe("Read receipts", () => { goTo(room1); assertStillRead(room2); }); - // XXX: fails because we see a dot instead of an unread number - probably the server and client disagree - it.skip("Editing a message after marking as read makes the room unread", () => { + it("Editing a message after marking as read makes the room unread", () => { // Given the room is marked as read goTo(room1); receiveMessages(room2, ["Msg1"]); @@ -146,8 +145,8 @@ describe("Read receipts", () => { // When a message is edited receiveMessages(room2, [editOf("Msg1", "Msg1 Edit1")]); - // Then the room becomes unread - assertUnread(room2, 1); + // Then the room remains unread + assertStillRead(room2); }); it("Editing a reply after reading it makes the room unread", () => { // Given the room is all read