element-web/playwright/e2e/read-receipts
David Baker 281916fd96
Take the Threads Activity Centre out of labs (#12439)
* Take the TAC out of labs!

Requires https://github.com/matrix-org/matrix-react-sdk/pull/12438
and ideally https://github.com/matrix-org/matrix-react-sdk/pull/12418

* i18n

* Add test method

That's needed now we we don't include threads in the notif count in the tests

* One less labs setting

* Update snapshot

* Disable release announcement

* Unused import

* Fix some screenshots

* Fix all the unread test cases now room unreads don't include threads

* Fix more tests

* Even more test fixes

* Still more test fixes

* Oh goodness, it's more test fixes

* Fix selectors now there are 2 buttons called Threads

* Disable some tests that aren't passing

for reasons that don't appear releated to any of the TAC work, as
per the comment.

* Remove debugging

* Oops, removed too much
2024-04-29 15:30:19 +00:00
..
editing-messages.spec.ts Take the Threads Activity Centre out of labs (#12439) 2024-04-29 15:30:19 +00:00
high-level.spec.ts Take the Threads Activity Centre out of labs (#12439) 2024-04-29 15:30:19 +00:00
index.ts
missing-referents.spec.ts
new-messages.spec.ts Take the Threads Activity Centre out of labs (#12439) 2024-04-29 15:30:19 +00:00
reactions.spec.ts Take the Threads Activity Centre out of labs (#12439) 2024-04-29 15:30:19 +00:00
read-receipts.spec.ts Take the Threads Activity Centre out of labs (#12439) 2024-04-29 15:30:19 +00:00
readme.md
redactions.spec.ts Take the Threads Activity Centre out of labs (#12439) 2024-04-29 15:30:19 +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 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.