-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regression: E2EE DM setup header toolbox items #32712
Conversation
Looks like this PR is ready to merge! 🎉 |
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-6.10.0 #32712 +/- ##
=================================================
Coverage ? 56.58%
=================================================
Files ? 2502
Lines ? 55538
Branches ? 11471
=================================================
Hits ? 31426
Misses ? 21420
Partials ? 2692
Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
The tests you wrote don't actually test the issue that is being fixed. It is a nice addition, but we need an end-to-end test for this, or:
- Extract the header items filter logic to a hook and unit test that hook
- Unit test
RoomToolboxE2EESetup
component
One of these 3 should be enough for this
apps/meteor/client/views/room/Header/RoomToolbox/RoomToolboxE2EESetup.tsx
Show resolved
Hide resolved
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.
Left some comments. Overall I'm wondering on the complexity of these tests, if it makes sense to implement all those checks on the same test evaluation.
In general I'd like to see more atomic tests. For ex: in this case you're testing the header buttons visibility, but there's a lot of other components of the feature being tested. I like to see that you included tests for the whole UX for the save password state, but it could be a little more organized.
What I mean is, a describe for this whole flow, and then a test clause for each behaviour you're testing.
Please let me know if you wanna discuss any of these topics or if you disagree with anything. All feedback is welcome.
3209171
to
0d97c08
Compare
Implemented a E2E test to cover this case, but for some reason the test is always failing on CI, so removed the test from this PR, will implement the test in a separate PR and it would be tracked by this task |
Proposed changes (including videos or screenshots)
The E2EE room setup header was showing irrelevant toolbox items on DM rooms which were not applicable for DMs.
Issue(s)
Steps to test or reproduce
Further comments
E2EE2-45