It appears the bug with these tests was just that the MessageBuilder
wasn't setting the thread relation on the reply messages as this didn't
happen trying to repro it manually, so fix the builder and re-enable
the tests.
The flip side of this is that it implies buggy clients that don't
set thread relations properly will cause stuck notifs in Element Web.
I've filed this as https://github.com/element-hq/element-web/issues/26787
* Enable skipped test in `editing-messages.spec.ts`
* Enable 2 more tests in `editing-messages.spec.ts`
* Fix `A room where all threaded edits are read is still read after restart` integ test
* Fix `A room where all threaded edits are read is still read after restart` integ test
* WIP fix `A room where all threaded edits are read is still read after restart `
* WIP fix `A room where all threaded edits are read is still read after restart `
* Migrate read-receipts.spec.ts from Cypress to Playwright
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Update client.ts
* Serialise test message sending
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
---------
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Migrate most read-receipts tests from Cypress to Playwright
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Disable failing test
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Iterate
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
---------
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
