test: add back notification e2e tests#16975
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
|
|
|
|
…add-back-notification-e2e-tests
…ved clarity and functionality
|
…pdate related tests
|
…for better debugging
|
|
There was a problem hiding this comment.
Bug: Clean Up Debugging Statements
Remove temporary console.log debugging statements committed to the codebase.
e2e/specs/notifications/utils/mock-notification-trigger-server.ts#L68-L75
e2e/specs/notifications/utils/mock-notification-trigger-server.ts#L84-L91
e2e/specs/notifications/utils/mocks.ts#L127-L134
metamask-mobile/e2e/specs/notifications/utils/mocks.ts
Lines 127 to 134 in 8fe63c9
Was this report helpful? Give feedback by reacting with 👍 or 👎
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #16975 +/- ##
==========================================
+ Coverage 72.82% 73.14% +0.31%
==========================================
Files 2742 2758 +16
Lines 59587 59948 +361
Branches 9409 9470 +61
==========================================
+ Hits 43397 43851 +454
+ Misses 13440 13350 -90
+ Partials 2750 2747 -3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|



Description
We quarantined the notif tests as they were flaking. Running the tests in isolation seem to pass.
Run 1
Run 2
Creating this PR to see if we can run the notification tests as part of the full smoke runs.
It is a little weird how these tests fail. Looking at previous runs where they failed, it looks as if the mock APIs are being called?
https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8130d943-b958-4a71-a5fa-561040bcd5fb
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist