-
Notifications
You must be signed in to change notification settings - Fork 986
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
[DO NOT MERGE] test status-go changes in suggested fees #21941
Conversation
91% of end-end tests have passed
Failed tests (4)Click to expandClass TestCommunityMultipleDeviceMerged:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestDeepLinksOneDevice:
Expected to fail tests (1)Click to expandClass TestCommunityMultipleDeviceMerged:
Passed tests (51)Click to expandClass TestCommunityOneDeviceMerged:
Class TestCommunityMultipleDeviceMerged:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestWalletOneDevice:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestActivityMultipleDevicePRTwo:
Class TestActivityMultipleDevicePR:
Class TestFallbackMultipleDevice:
Class TestWalletMultipleDevice:
Class TestDeepLinksOneDevice:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestActivityCenterContactRequestMultipleDevicePR:
|
@briansztamfater thank you for PR. Take a look found issue: ISSUE 1: Estimated time and max fee shown as "unknown" on approve and swap confirmation drawerSteps:
Actual result:Estimated time and max fee shown as "unknown" Expected result:Max fee and estimated time is fetched:
|
The issue mentioned in this comment is not introduced by the current related Status Go PR (status-go#6243). This issue already exists in Status Go, as I verified in another mobile PR (status-mobile#21876) that also includes the status go. This means the current PR is not blocked by this issue. However, it should still be addressed because once we bump Status Go to our mobile develop branch, the issue will appear there as well. I’ve reported it separately #21948. @briansztamfater @saledjenic Could you please take a look at this issue requires some UI adjustments, or is it a Go-related problem? |
@briansztamfater Thank you for creating this PR. Just confirmed status-im/status-go#6243 (comment) merging status go PR |
75% of end-end tests have passed
Failed tests (1)Click to expandClass TestCommunityMultipleDeviceMergedTwo:
Passed tests (3)Click to expandClass TestDeepLinksOneDevice:
Class TestCommunityMultipleDeviceMerged:
|
There are some sensitive changes being made in the router status-im/status-go#6243
So before merging that status-go PR, it would be great if someone from the @status-im/mobile-qa team could briefly smoke test our wallet main flows in this PR that includes those changes.
This PR will not be merged, its just for testing purposes.