element-web/cypress/e2e/read-receipts
Andy Balaam 03b2246068
Disable flaky test 'Reading a thread after a reaction to a redacted message marks the thread as read' (#11890)
2023-11-16 10:21:13 +00:00
..
editing-messages.spec.ts Fix a test that was expecting an edit to be considered unread (#11847) 2023-11-11 08:42:02 +00:00
high-level.spec.ts
missing-referents.spec.ts
new-messages.spec.ts
reactions.spec.ts
read-receipts-utils.ts
read-receipts.spec.ts
readme.md
redactions.spec.ts Disable flaky test 'Reading a thread after a reaction to a redacted message marks the thread as read' (#11890) 2023-11-16 10:21:13 +00:00

readme.md

High Level Read Receipt Tests

Tips for writing these tests:

  • Break up your tests into the smallest test case possible. The purpose of these tests is to understand hard-to-find bugs, so small tests are necessary. We know that Cypress recommends combining tests together for performance, but that will frustrate our goals here. (We will need to find a different way to reduce CI time.)

  • Try to assert something after every action, to make sure it has completed. E.g.: markAsRead(room2); assertRead(room2); You should especially follow this rule if you are jumping to a different room or similar straight afterwards.

  • Use assertStillRead() if you are asserting something is read when it was also read before. This waits a little while to make sure you're not getting a false positive.