Skip to content
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

Quo2: fix reaction styles #17224

Merged
merged 1 commit into from
Sep 14, 2023
Merged

Quo2: fix reaction styles #17224

merged 1 commit into from
Sep 14, 2023

Conversation

clauxx
Copy link
Member

@clauxx clauxx commented Sep 8, 2023

fixes #16907

Summary

Based on the following feedback comment, the size of the reaction and add-reaction components were off from the designs. Additionally, fixed the colors based on the Design System component.

Testing notes

  1. Noticed that the Use Case property from the Design System is not included in the component. Could be added as a follow up issue.
  2. Additional to the sizes, fixed the background/border colors as they were different from the designs

Platforms

  • Android
  • iOS

Steps to test

  • Open Status
  • Check the component in the Preview menu

status: ready

@clauxx clauxx self-assigned this Sep 8, 2023
@status-github-bot status-github-bot bot added this to REVIEW in Pipeline for QA Sep 8, 2023
@status-im-auto
Copy link
Member

status-im-auto commented Sep 8, 2023

Jenkins Builds

Click to see older builds (20)
Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ f0a912b #1 2023-09-08 09:49:49 ~6 min android-e2e 🤖apk 📲
✔️ f0a912b #1 2023-09-08 09:50:52 ~7 min android 🤖apk 📲
✔️ f0a912b #1 2023-09-08 09:51:59 ~8 min tests 📄log
✔️ f0a912b #1 2023-09-08 09:53:46 ~10 min ios 📱ipa 📲
✔️ 8185e86 #2 2023-09-11 10:32:40 ~5 min android-e2e 🤖apk 📲
✔️ 8185e86 #2 2023-09-11 10:33:07 ~5 min android 🤖apk 📲
✔️ 8185e86 #2 2023-09-11 10:36:06 ~8 min tests 📄log
✔️ 8185e86 #2 2023-09-11 10:38:40 ~11 min ios 📱ipa 📲
✔️ 3af0daf #3 2023-09-11 11:45:41 ~6 min ios 📱ipa 📲
✔️ 3af0daf #3 2023-09-11 11:48:57 ~10 min android 🤖apk 📲
✔️ 3af0daf #3 2023-09-11 11:48:58 ~10 min android-e2e 🤖apk 📲
✔️ 3af0daf #3 2023-09-11 11:49:07 ~10 min tests 📄log
✔️ e32d7e0 #4 2023-09-11 12:59:52 ~6 min android-e2e 🤖apk 📲
✔️ e32d7e0 #4 2023-09-11 13:00:21 ~6 min android 🤖apk 📲
✔️ e32d7e0 #4 2023-09-11 13:04:04 ~10 min tests 📄log
✔️ e32d7e0 #4 2023-09-11 13:06:24 ~12 min ios 📱ipa 📲
✔️ 2fa3097 #5 2023-09-12 09:07:06 ~5 min android-e2e 🤖apk 📲
✔️ 2fa3097 #5 2023-09-12 09:10:06 ~8 min android 🤖apk 📲
✔️ 2fa3097 #5 2023-09-12 09:11:11 ~9 min tests 📄log
✔️ 2fa3097 #5 2023-09-12 09:20:26 ~18 min ios 📱ipa 📲
Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ 7bfb341 #6 2023-09-14 08:07:42 ~5 min android 🤖apk 📲
✔️ 7bfb341 #6 2023-09-14 08:09:18 ~7 min ios 📱ipa 📲
✔️ 7bfb341 #6 2023-09-14 08:09:35 ~7 min android-e2e 🤖apk 📲
✔️ 7bfb341 #6 2023-09-14 08:11:34 ~9 min tests 📄log
✔️ 6842223 #7 2023-09-14 08:51:43 ~5 min android-e2e 🤖apk 📲
✔️ 6842223 #7 2023-09-14 08:52:50 ~6 min ios 📱ipa 📲
✔️ 6842223 #7 2023-09-14 08:54:13 ~8 min android 🤖apk 📲
✔️ 6842223 #7 2023-09-14 08:56:11 ~10 min tests 📄log

@@ -12,31 +12,32 @@
[rn/touchable-opacity
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: the name space of this component is wrong - it's not to do with your changes but perhaps while you are working on these files you can migrate it to the correct location?
I.e these should be in .selectors. To match figma and the name should match that of figma.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additionally these files should only export one component and it seems like this file has two in it, can we adjust that and map with fi hmm a 1-1 as we have in the rest of our components? Makes things easier to maintain and to understand what we have in place etc 🙂

:flex-direction :row
:align-items :center}
[quo2.reaction/reaction @state]
[quo2.reaction/add-reaction @state]]]])))
[quo/reaction @state]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for these preview screens, we should only have one design system component per preview screen- could you fix this here or as a follow up? 🙏

Copy link
Member Author

@clauxx clauxx Sep 8, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was thinking the same. I think as a follow-up might be better, cause the component also seems incomplete (is missing a prop from the DS)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds great, maybe we can some simple unit tests in that too and align some other best practices :)

@clauxx clauxx requested a review from J-Son89 September 8, 2023 09:57
@VolodLytvynenko VolodLytvynenko self-assigned this Sep 8, 2023
@VolodLytvynenko VolodLytvynenko moved this from REVIEW to E2E Tests in Pipeline for QA Sep 8, 2023
@status-im-auto
Copy link
Member

67% of end-end tests have passed

Total executed tests: 43
Failed tests: 14
Passed tests: 29
IDs of failed tests: 702732,703495,703086,702894,702783,703297,703503,703496,703202,702786,702807,702731,702808,702958 

Failed tests (14)

Click to expand
  • Rerun failed tests

  • Class TestCommunityOneDeviceMerged:

    1. test_community_discovery, id: 703503
    Test is not run, e2e blocker  
    

    [[reason: [NOTRUN] https://github.com//issues/17175]]

    Class TestActivityMultipleDevicePRTwo:

    1. test_activity_center_admin_notification_accept_swipe, id: 702958

    Device 2: Find Button by xpath: //*[@content-desc='password-input']/../following-sibling::*//*[@text='Join Community']
    Device 2: Tap on found: Button

    medium/test_activity_center.py:385: in test_activity_center_admin_notification_accept_swipe
        self.community_2.join_community()
    ../views/chat_view.py:424: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: Text by accessibility id:`status-tag-positive` is not found on the screen after wait_for_visibility_of_element
    



    Device sessions

    Class TestCommunityMultipleDeviceMerged:

    1. test_community_mark_all_messages_as_read, id: 703086

    Device 1: Tap on found: Button
    Device 1: Click until Text by accessibility id: community-description-text will be presented

    critical/test_public_chat_browsing.py:1028: in test_community_mark_all_messages_as_read
        self.errors.verify_no_errors()
    base_test_case.py:191: in verify_no_errors
        pytest.fail('\n '.join([self.errors.pop(0) for _ in range(len(self.errors))]))
     New messages counter is not shown in home > Community element
    E    New messages counter is not shown in community channel element
    



    Device sessions

    2. test_community_contact_block_unblock_offline, id: 702894

    Device 1: Click until ChatMessageInput by accessibility id: chat-message-input will be presented
    Device 1: Looking for a message by text: Hurray! unblocked

    critical/test_public_chat_browsing.py:967: in test_community_contact_block_unblock_offline
        self.errors.verify_no_errors()
    base_test_case.py:191: in verify_no_errors
        pytest.fail('\n '.join([self.errors.pop(0) for _ in range(len(self.errors))]))
     Hurray! unblocked was not received in public chat after user unblock!
    



    Device sessions

    Class TestGroupChatMultipleDeviceMergedNewUI:

    1. test_group_chat_pin_messages, id: 702732

    Test is not run, e2e blocker  
    

    [[reason: [NOTRUN] Pin feature is in development]]

    2. test_group_chat_mute_chat, id: 703495

    Test setup failed: critical/chats/test_group_chat.py:202: in prepare_devices
        self.chats[0] = self.homes[0].create_group_chat(user_names_to_add=[self.usernames[1], self.usernames[2]]</b>,
    ../views/home_view.py:412: in create_group_chat
        chat.chat_name_editbox.send_keys(group_chat_name)
    ../views/base_element.py:367: in send_keys
        self.find_element().send_keys(value)
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 1: EditBox by accessibility id: `chat-name-input` is not found on the screen; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#no-such-element-exception
    



    3. test_group_chat_send_image_save_and_share, id: 703297

    Test setup failed: critical/chats/test_group_chat.py:202: in prepare_devices
        self.chats[0] = self.homes[0].create_group_chat(user_names_to_add=[self.usernames[1], self.usernames[2]]</b>,
    ../views/home_view.py:412: in create_group_chat
        chat.chat_name_editbox.send_keys(group_chat_name)
    ../views/base_element.py:367: in send_keys
        self.find_element().send_keys(value)
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 1: EditBox by accessibility id: `chat-name-input` is not found on the screen; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#no-such-element-exception
    



    4. test_group_chat_reactions, id: 703202

    Test setup failed: critical/chats/test_group_chat.py:202: in prepare_devices
        self.chats[0] = self.homes[0].create_group_chat(user_names_to_add=[self.usernames[1], self.usernames[2]]</b>,
    ../views/home_view.py:412: in create_group_chat
        chat.chat_name_editbox.send_keys(group_chat_name)
    ../views/base_element.py:367: in send_keys
        self.find_element().send_keys(value)
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 1: EditBox by accessibility id: `chat-name-input` is not found on the screen; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#no-such-element-exception
    



    5. test_group_chat_join_send_text_messages_push, id: 702807

    Device 1: Tap on found: Button
    Device 1: Find EditBox by accessibility id: chat-name-input

    Test setup failed: critical/chats/test_group_chat.py:202: in prepare_devices
        self.chats[0] = self.homes[0].create_group_chat(user_names_to_add=[self.usernames[1], self.usernames[2]]</b>,
    ../views/home_view.py:412: in create_group_chat
        chat.chat_name_editbox.send_keys(group_chat_name)
    ../views/base_element.py:367: in send_keys
        self.find_element().send_keys(value)
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 1: EditBox by accessibility id: `chat-name-input` is not found on the screen; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#no-such-element-exception
    



    Device sessions

    6. test_group_chat_offline_pn, id: 702808

    Test setup failed: critical/chats/test_group_chat.py:202: in prepare_devices
        self.chats[0] = self.homes[0].create_group_chat(user_names_to_add=[self.usernames[1], self.usernames[2]]</b>,
    ../views/home_view.py:412: in create_group_chat
        chat.chat_name_editbox.send_keys(group_chat_name)
    ../views/base_element.py:367: in send_keys
        self.find_element().send_keys(value)
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 1: EditBox by accessibility id: `chat-name-input` is not found on the screen; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#no-such-element-exception
    



    Class TestCommunityMultipleDeviceMergedTwo:

    1. test_community_mentions_push_notification, id: 702786

    # STEP: Invited member gets push notification with the mention and tap it
    Device 2: Getting PN by 'user_2'

    critical/test_public_chat_browsing.py:1149: in test_community_mentions_push_notification
        self.errors.verify_no_errors()
    base_test_case.py:191: in verify_no_errors
        pytest.fail('\n '.join([self.errors.pop(0) for _ in range(len(self.errors))]))
     Push notification with the mention was not received by admin
    E    Can not edit a message with a mention
    E    Push notification with the mention was not received by the invited member 
    

    [[Issue with username in PN, issue #6 in 15500]]

    Device sessions

    Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:

    1. test_1_1_chat_is_shown_message_sent_delivered_from_offline, id: 702783

    Device 2: Find Text by xpath: //*[starts-with(@text,'test message')]/ancestor::android.view.ViewGroup[@content-desc='chat-item']//*[@content-desc='message-status']/android.widget.TextView
    Device 2: Text is Sent

    critical/chats/test_1_1_public_chats.py:1416: in test_1_1_chat_is_shown_message_sent_delivered_from_offline
        self.errors.verify_no_errors()
    base_test_case.py:191: in verify_no_errors
        pytest.fail('\n '.join([self.errors.pop(0) for _ in range(len(self.errors))]))
     Message was not delivered after resending from offline
    E    Message status was not changed to Delivered, it's Sent after back up online!
    



    Device sessions

    2. test_1_1_chat_mute_chat, id: 703496

    Device 1: Click until ChatMessageInput by accessibility id: chat-message-input will be presented
    Device 1: Looking for a message by text: after unmute

    critical/chats/test_1_1_public_chats.py:1457: in test_1_1_chat_mute_chat
        self.errors.verify_no_errors()
    base_test_case.py:191: in verify_no_errors
        pytest.fail('\n '.join([self.errors.pop(0) for _ in range(len(self.errors))]))
     Message text 'should be muted' is not shown in chat preview after mute
    E    Message 'should be muted' is not shown in chat for receiver after mute
    



    Device sessions

    Class TestOneToOneChatMultipleSharedDevicesNewUi:

    1. test_1_1_chat_pin_messages, id: 702731

    Test is not run, e2e blocker  
    

    [[reason: [NOTRUN] Pin feature is in development]]

    Passed tests (29)

    Click to expand

    Class TestCommunityOneDeviceMerged:

    1. test_restore_multiaccount_with_waku_backup_remove_switch, id: 703133
    Device sessions

    2. test_community_copy_and_paste_message_in_chat_input, id: 702742
    Device sessions

    3. test_community_undo_delete_message, id: 702869
    Device sessions

    4. test_community_navigate_to_channel_when_relaunch, id: 702846
    Device sessions

    5. test_community_mute_community_and_channel, id: 703382
    Device sessions

    Class TestActivityMultipleDevicePRTwo:

    1. test_activity_center_mentions, id: 702957
    Device sessions

    Class TestCommunityMultipleDeviceMerged:

    1. test_community_several_images_send_reply, id: 703194
    Device sessions

    2. test_community_one_image_send_reply, id: 702859
    Device sessions

    3. test_community_emoji_send_copy_paste_reply, id: 702840
    Device sessions

    4. test_community_message_delete, id: 702839
    Device sessions

    5. test_community_message_send_check_timestamps_sender_username, id: 702838
    Device sessions

    6. test_community_links_with_previews_github_youtube_twitter_gif_send_enable, id: 702844
    Device sessions

    7. test_community_message_edit, id: 702843
    Device sessions

    8. test_community_unread_messages_badge, id: 702841
    Device sessions

    Class TestActivityCenterContactRequestMultipleDevicePR:

    1. test_activity_center_contact_request_accept_swipe_mark_all_as_read, id: 702851
    Device sessions

    2. test_activity_center_contact_request_decline, id: 702850
    Device sessions

    Class TestActivityMultipleDevicePR:

    1. test_navigation_jump_to, id: 702936
    Device sessions

    2. test_activity_center_reply_read_unread_delete_filter_swipe, id: 702947
    Device sessions

    Class TestCommunityMultipleDeviceMergedTwo:

    1. test_community_markdown_support, id: 702809
    Device sessions

    2. test_community_hashtag_links_to_community_channels, id: 702948
    Device sessions

    3. test_community_leave, id: 702845
    Device sessions

    Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:

    1. test_1_1_chat_delete_via_long_press_relogin, id: 702784
    Device sessions

    Class TestOneToOneChatMultipleSharedDevicesNewUi:

    1. test_1_1_chat_emoji_send_reply_and_open_link, id: 702782
    Device sessions

    2. test_1_1_chat_text_message_delete_push_disappear, id: 702733
    Device sessions

    3. test_1_1_chat_push_emoji, id: 702813
    Device sessions

    4. test_1_1_chat_non_latin_messages_stack_update_profile_photo, id: 702745
    Device sessions

    5. test_1_1_chat_edit_message, id: 702855
    Device sessions

    6. test_1_1_chat_send_image_save_and_share, id: 703391
    Device sessions

    7. test_1_1_chat_message_reaction, id: 702730
    Device sessions

    @VolodLytvynenko VolodLytvynenko removed their assignment Sep 8, 2023
    @pavloburykh pavloburykh self-assigned this Sep 8, 2023
    @pavloburykh pavloburykh moved this from E2E Tests to IN TESTING in Pipeline for QA Sep 8, 2023
    @pavloburykh
    Copy link
    Contributor

    Ready for design review cc @Francesca-G

    @pavloburykh pavloburykh moved this from IN TESTING to Design review in Pipeline for QA Sep 8, 2023
    Copy link

    @Francesca-G Francesca-G left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    The component looks good when tested in a chat, reacting to a message but when I open it from the Quo2 Preview -> selectors -> select-reactions it looks different:

    IMG_0670

    is this supposed to happen?
    (Also, once I opened it I had to close the application, because there was no back button in the preview).

    Moreover, we should discuss with Pedro and the rest of the team about a solution for the emoji library. We're supposed to use twemoji, so the component is correct, but since we're using system emoji for the time being we should adapt the component to the system ones, to be consistent. Otherwise we will have reactions with twemoji + system emojis in messages.

    @OmarBasem - this sounds related to recent nav bar changes, do you know if that's all working fine?
    is this supposed to happen?
    (Also, once I opened it I had to close the application, because there was no back button in the preview).

    with respect to twemoji etc @smohamedjavid has researched this area a lot recently and can probably provide some input on this? 🤨

    @clauxx
    Copy link
    Member Author

    clauxx commented Sep 11, 2023

    @Francesca-G Sorry, didn't add the exact location in the preview. The component was originally located in the wrong place (under reactions instead of selectors) and will fix that in a follow-up. Also the component is missing the Use Case property, so might as well add it in the follow-up as well. What do you think?

    @Francesca-G
    Copy link

    @clauxx sure, adding the follow up required tag

    @smohamedjavid
    Copy link
    Member

    is this supposed to happen? (Also, once I opened it I had to close the application, because there was no back button in the preview).

    We need to update the preview screen for reactions (status-im2.contexts.quo-preview.selectors.reactions ns) to use the new preview-container component which has the navigation bar. Apologies for that. Gesture navigation (back) would work on Quo2 previews.

    with respect to twemoji etc @smohamedjavid has researched this area a lot recently and can probably provide some input on this? 🤨

    @Francesca-G - The team decided to defer Twemoji integration in the mobile. It will be implemented post-MVP. We will be using the default emojis from the OS (Android or iOS) until then.

    @Francesca-G
    Copy link

    @Francesca-G - The team decided to defer Twemoji integration in the mobile. It will be implemented post-MVP. We will be using the default emojis from the OS (Android or iOS) until then.

    Ok good, so we should adapt the react component so that it aligns with the default emojis and we have a consistent style throughout :)

    @smohamedjavid
    Copy link
    Member

    @Francesca-G - The team decided to defer Twemoji integration in the mobile. It will be implemented post-MVP. We will be using the default emojis from the OS (Android or iOS) until then.

    Ok good, so we should adapt the react component so that it aligns with the default emojis and we have a consistent style throughout :)

    I believe the Twemoji (and default emojis) is not applicable to the reactions as the reaction emojis are unique and limited to 6. These emojis are the same as the desktop despite the desktop uses Twemoji.
    https://www.figma.com/file/qLLuMLfpGxK9OfpIavwsmK/Iconset?type=design&node-id=942%3A218&mode=design&t=POPE62tL4H0Dd0YU-1

    @Francesca-G
    Copy link

    @smohamedjavid as mentioned by Pedro, ideally the reaction emojis should be the same as what the user can send in messages, so we should adapt this component to OS emojis. Is that possible?

    @smohamedjavid
    Copy link
    Member

    @smohamedjavid as mentioned by Pedro, ideally the reaction emojis should be the same as what the user can send in messages, so we should adapt this component to OS emojis. Is that possible?

    It's possible. We need to remove the existing custom reaction images/emojis and add the equivalent default OS emoji for the reaction.

    BTW this is a completely new change and requires separate testing effort. We will need a separate issue to track it.

    cc: @flexsurfer

    @clauxx
    Copy link
    Member Author

    clauxx commented Sep 12, 2023

    @cammellos @J-Son89 can you please merge it? I'm not authorized 😢

    @OmarBasem
    Copy link
    Member

    this sounds related to recent nav bar changes, do you know if that's all working fine?
    is this supposed to happen?

    The file status-im2.contexts.quo-preview.selectors.reactions seems got missed in the migrations. It needs to be wrapped with the new preview container.

    @clauxx
    Copy link
    Member Author

    clauxx commented Sep 12, 2023

    this sounds related to recent nav bar changes, do you know if that's all working fine?
    is this supposed to happen?

    The file status-im2.contexts.quo-preview.selectors.reactions seems got missed in the migrations. It needs to be wrapped with the new preview container.

    Can take care of that in the follow-up issue

    @clauxx clauxx merged commit 5d4fbe7 into develop Sep 14, 2023
    6 checks passed
    Pipeline for QA automation moved this from Design review to DONE Sep 14, 2023
    @clauxx clauxx deleted the 16907-fix-reaction-styles branch September 14, 2023 09:21
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    Archived in project
    Development

    Successfully merging this pull request may close these issues.

    Emojis boxes is bigger than in design - comment here
    8 participants