riot-web/playwright/e2e/read-receipts
Michael Telatynski f7a078d250
Update right panel base card styling to match Compound (#12768)
* Update base card styling to match Compound

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

* Update screenshot

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

---------

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2024-07-16 09:03:35 +00:00
..
editing-messages-in-threads.spec.ts
editing-messages-main-timeline.spec.ts
editing-messages-thread-roots.spec.ts
high-level.spec.ts
index.ts Update right panel base card styling to match Compound (#12768) 2024-07-16 09:03:35 +00:00
message-ordering.spec.ts
missing-referents.spec.ts
new-messages-in-threads.spec.ts
new-messages-main-timeline.spec.ts
new-messages-thread-roots.spec.ts
notifications.spec.ts
reactions-in-threads.spec.ts
reactions-main-timeline.spec.ts
reactions-thread-roots.spec.ts
read-receipts.spec.ts
readme.md
redactions-in-threads.spec.ts
redactions-main-timeline.spec.ts
redactions-thread-roots.spec.ts
room-list-order.spec.ts

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 Playwright 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 afterward.

  • 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.