-
-
Notifications
You must be signed in to change notification settings - Fork 831
Split the read-receipt tests into logical units #11649
Conversation
25cf817
to
82e65c8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's hard to do a comprehensive review of this, but the general principle seems sensible.
*/ | ||
|
||
/* | ||
* # High Level Read Receipt Tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also, presumably only high-level.spec.ts
are "High Level" tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still consider all of these high level. I avoided renaming the "high-level" file as "misc" because I didn't like that name and it made it easer for me to preserve my later PRs.
I am kind of hoping that when we flesh out more tests inside that file they will earn their own separate files with good names.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok. It might be good to create a high-level
subdirectory then?
Part of element-hq/element-web#25449
This should prevent them being super-slow on CI, and crashing Chrome.
This change is marked as an internal change (Task), so will not be included in the changelog.