-
Notifications
You must be signed in to change notification settings - Fork 260
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
task(crypto_tests): Re-shape tests for UtdCause #4349
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4349 +/- ##
==========================================
- Coverage 85.18% 85.16% -0.02%
==========================================
Files 280 280
Lines 30729 30729
==========================================
- Hits 26176 26170 -6
- Misses 4553 4559 +6 ☔ View full report in Codecov by Sentry. |
778dc5d
to
914b7cd
Compare
Rebased on top of CI fixes. No changes to my commits except updated their descriptions. |
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.
Just a minor comment, if we could have const for 1111 / 5555 / 9999 to show the relation between them as it is important (5555 should be in between the 2 others)
…r UnableToDecryptInfos
…rrectly This test was checking that a new device which has access to backups returned an unknown UTD when it was given empty JSON for the event. It was only passing because we currently have incorrect behaviour when backups are enabled. The fix is to make the device old and without access to backups, so that we still consider this UTD unexpected.
5db4563
to
0b89ba9
Compare
Part of element-hq/element-meta#2638
If you review commit by commit you will see explanations for what I did, but you will read more code in total.