Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

Fill cypress test high-level.spec.ts > A receipt for the last unimportant event makes the room read, even if all are unimportant #11830

Merged

Conversation

florianduros
Copy link
Contributor

@florianduros florianduros commented Nov 6, 2023

Checklist

  • Tests written for new code (and old code if feasible)
  • Linter and other CI checks pass
  • Sign-off given on the changes (see CONTRIBUTING.md)

Fill cypress test high-level.spec.ts > A receipt for the last unimportant event makes the room read, even if all are unimportant

Part of element-hq/element-web#25449


This change is marked as an internal change (Task), so will not be included in the changelog.

…portant event makes the room read, even if all are unimportant`
@florianduros florianduros added the T-Task Refactoring, enabling or disabling functionality, other engineering tasks label Nov 6, 2023
@florianduros florianduros marked this pull request as ready for review November 6, 2023 14:32
@florianduros florianduros requested a review from a team as a code owner November 6, 2023 14:32
@@ -168,7 +168,23 @@ describe("Read receipts", () => {
// The room is unread again
assertUnread(room2, 1);
});
it.skip("A receipt for the last unimportant event makes the room read, even if all are unimportant", () => {});
it("A receipt for the last unimportant event makes the room read, even if all are unimportant", () => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if the intention of this test was that the room should start off unread?

@andybalaam as the guardian of these tests I think this is one for you

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, this is just to say that unimportant events that are read don't make the room unread, so I think this is good modulo the comment I made.

Copy link
Member

@andybalaam andybalaam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good with 1 change. Thanks!

cypress/e2e/read-receipts/high-level.spec.ts Outdated Show resolved Hide resolved
cypress/e2e/read-receipts/high-level.spec.ts Outdated Show resolved Hide resolved
cypress/e2e/read-receipts/high-level.spec.ts Outdated Show resolved Hide resolved
cypress/e2e/read-receipts/high-level.spec.ts Outdated Show resolved Hide resolved
@@ -168,7 +168,23 @@ describe("Read receipts", () => {
// The room is unread again
assertUnread(room2, 1);
});
it.skip("A receipt for the last unimportant event makes the room read, even if all are unimportant", () => {});
it("A receipt for the last unimportant event makes the room read, even if all are unimportant", () => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, this is just to say that unimportant events that are read don't make the room unread, so I think this is good modulo the comment I made.

Copy link
Member

@andybalaam andybalaam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thanks!

@florianduros florianduros added this pull request to the merge queue Nov 8, 2023
Merged via the queue into develop with commit b1e283d Nov 8, 2023
22 checks passed
@florianduros florianduros deleted the florianduros/unread/read-after-unimportant-messages branch November 8, 2023 09:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
T-Task Refactoring, enabling or disabling functionality, other engineering tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants