-
Notifications
You must be signed in to change notification settings - Fork 985
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
[#17288] refactor: migrate previews to new api #17420
Conversation
Jenkins BuildsClick to see older builds (4)
|
48b26ca
to
e95bba7
Compare
44% of end-end tests have passed
Failed tests (24)Click to expandClass TestActivityCenterContactRequestMultipleDevicePR:
Class TestActivityMultipleDevicePR:
Class TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Passed tests (19)Click to expandClass TestActivityMultipleDevicePRTwo:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
|
@status-im/mobile-qa all changes are related to just quo preview screens. does it need manual qa? |
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.
LGTM!
Good question. In my experience, changes related to 'quo' do not introduce additional issues. Perhaps we should consider PRs like this for direct movement to design review |
Thanks for the ping @mohsen-ghafouri 🙏 |
Thats correct #17420 (comment) @qoqobolo Thank you! hi @Francesca-G could you take a look, please? |
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.
Looks good :)
Issue, not design-related: when finishing the onboarding flow the app crashed, right after pressing "Start using Status". I reopened and it worked normally after that first crash
e95bba7
to
4892cb0
Compare
to accomplish #17288
migrated :
status: ready