riot-web/cypress/e2e/read-receipts
Andy Balaam 5c9e7baa78
Merge pull request #11854 from matrix-org/andybalaam/disable-flaking-pageup-test
Disable 'Looking in thread view to find old threads...' because of flakes
2023-11-11 07:09:30 +00:00
..
editing-messages.spec.ts Disable everywhere since we saw another flake 2023-11-10 11:40:08 +00:00
high-level.spec.ts Disable 'Looking in thread view to find old threads...' because of flakes 2023-11-10 15:31:54 +00:00
missing-referents.spec.ts
new-messages.spec.ts
reactions.spec.ts Test for adding and removing a reaction in a thread (#11839) 2023-11-09 15:09:03 +00:00
read-receipts-utils.ts Increase the timeout for the bot to enter the room (#11742) 2023-10-13 08:50:16 +00:00
read-receipts.spec.ts
readme.md
redactions.spec.ts Enable tests fixed by https://github.com/matrix-org/matrix-js-sdk/pull/3817 (#11781) 2023-11-09 14:47:14 +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.