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

Implement alert banner #19011

Merged
merged 1 commit into from
Mar 12, 2024
Merged

Implement alert banner #19011

merged 1 commit into from
Mar 12, 2024

Conversation

Parveshdhull
Copy link
Member

@Parveshdhull Parveshdhull commented Feb 27, 2024

fixes #19007

output-2024-03-03_18.15.37.mp4

status: ready

@status-github-bot status-github-bot bot added this to REVIEW in Pipeline for QA Feb 27, 2024
@status-im-auto
Copy link
Member

status-im-auto commented Feb 27, 2024

Jenkins Builds

Click to see older builds (60)
Commit #️⃣ Finished (UTC) Duration Platform Result
3b29cfa #1 2024-02-27 09:48:27 ~1 min tests 📄log
✔️ 3b29cfa #1 2024-02-27 09:54:16 ~7 min android 🤖apk 📲
✔️ 3b29cfa #1 2024-02-27 09:54:19 ~7 min android-e2e 🤖apk 📲
✔️ 3b29cfa #1 2024-02-27 09:56:06 ~9 min ios 📱ipa 📲
55cc829 #2 2024-02-27 12:35:43 ~2 min tests 📄log
✔️ 55cc829 #2 2024-02-27 12:41:17 ~7 min android-e2e 🤖apk 📲
✔️ 55cc829 #2 2024-02-27 12:41:17 ~7 min android 🤖apk 📲
✔️ 55cc829 #2 2024-02-27 12:42:51 ~9 min ios 📱ipa 📲
b062eac #3 2024-02-27 13:19:26 ~2 min tests 📄log
✔️ b062eac #3 2024-02-27 13:24:30 ~7 min android-e2e 🤖apk 📲
✔️ b062eac #3 2024-02-27 13:24:46 ~7 min android 🤖apk 📲
✔️ b062eac #3 2024-02-27 13:29:33 ~12 min ios 📱ipa 📲
87dd1b0 #10 2024-02-27 15:39:19 ~44 min tests 📄log
✔️ 87dd1b0 #10 2024-02-27 15:41:13 ~46 min android 🤖apk 📲
✔️ 87dd1b0 #10 2024-02-27 15:41:43 ~46 min android-e2e 🤖apk 📲
✔️ 87dd1b0 #10 2024-02-27 17:11:18 ~2 hr 16 min ios 📱ipa 📲
9e1fcc9 #11 2024-02-28 08:29:29 ~2 min tests 📄log
✔️ 9e1fcc9 #11 2024-02-28 08:34:48 ~7 min android-e2e 🤖apk 📲
✔️ 9e1fcc9 #11 2024-02-28 08:34:52 ~7 min android 🤖apk 📲
✔️ 9e1fcc9 #11 2024-02-28 08:37:32 ~10 min ios 📱ipa 📲
8655aef #12 2024-02-28 12:46:37 ~1 min tests 📄log
✔️ 8655aef #12 2024-02-28 12:52:19 ~7 min android-e2e 🤖apk 📲
✔️ 8655aef #12 2024-02-28 12:52:23 ~7 min android 🤖apk 📲
✔️ 8655aef #12 2024-02-28 12:55:35 ~10 min ios 📱ipa 📲
2a40dd5 #13 2024-02-28 13:02:20 ~1 min tests 📄log
✔️ 2a40dd5 #13 2024-02-28 13:07:04 ~6 min android-e2e 🤖apk 📲
✔️ 2a40dd5 #13 2024-02-28 13:07:18 ~6 min android 🤖apk 📲
✔️ 2a40dd5 #13 2024-02-28 13:10:53 ~10 min ios 📱ipa 📲
7d3d077 #14 2024-02-28 13:20:50 ~3 min tests 📄log
✔️ 7d3d077 #14 2024-02-28 13:25:15 ~7 min android 🤖apk 📲
✔️ 7d3d077 #14 2024-02-28 13:25:37 ~8 min android-e2e 🤖apk 📲
✔️ 7d3d077 #14 2024-02-28 13:27:51 ~10 min ios 📱ipa 📲
✔️ f5153d7 #16 2024-03-03 12:59:33 ~6 min tests 📄log
✔️ f5153d7 #16 2024-03-03 12:59:45 ~6 min android 🤖apk 📲
✔️ f5153d7 #16 2024-03-03 13:01:03 ~7 min android-e2e 🤖apk 📲
✔️ f5153d7 #16 2024-03-03 13:06:17 ~13 min ios 📱ipa 📲
✔️ c110d1e #17 2024-03-04 13:34:42 ~6 min android 🤖apk 📲
✔️ c110d1e #17 2024-03-04 13:34:43 ~6 min tests 📄log
✔️ c110d1e #17 2024-03-04 13:36:05 ~7 min android-e2e 🤖apk 📲
✔️ c110d1e #17 2024-03-04 13:43:51 ~15 min ios 📱ipa 📲
2a15359 #19 2024-03-04 15:16:22 ~1 min tests 📄log
✔️ 2a15359 #19 2024-03-04 15:21:12 ~6 min android 🤖apk 📲
✔️ 2a15359 #19 2024-03-04 15:21:51 ~7 min android-e2e 🤖apk 📲
✔️ 2a15359 #19 2024-03-04 15:24:14 ~9 min ios 📱ipa 📲
✔️ 0b7aa41 #20 2024-03-04 15:56:08 ~6 min tests 📄log
✔️ 0b7aa41 #20 2024-03-04 15:56:44 ~7 min android-e2e 🤖apk 📲
✔️ 0b7aa41 #20 2024-03-04 15:56:48 ~7 min android 🤖apk 📲
✔️ 0b7aa41 #20 2024-03-04 16:02:12 ~12 min ios 📱ipa 📲
206a493 #21 2024-03-04 16:26:15 ~1 min tests 📄log
✔️ 206a493 #21 2024-03-04 16:31:37 ~6 min android 🤖apk 📲
✔️ 206a493 #21 2024-03-04 16:31:38 ~6 min android-e2e 🤖apk 📲
✔️ 206a493 #21 2024-03-04 16:34:42 ~9 min ios 📱ipa 📲
✔️ 19c236a #22 2024-03-04 17:26:58 ~7 min tests 📄log
✔️ 19c236a #22 2024-03-04 17:27:26 ~7 min ios 📱ipa 📲
✔️ 19c236a #22 2024-03-04 17:28:30 ~8 min android-e2e 🤖apk 📲
✔️ 19c236a #22 2024-03-04 17:28:31 ~8 min android 🤖apk 📲
✔️ b86c28f #23 2024-03-07 09:43:02 ~6 min tests 📄log
✔️ b86c28f #23 2024-03-07 09:45:19 ~8 min android-e2e 🤖apk 📲
✔️ b86c28f #23 2024-03-07 09:45:23 ~8 min android 🤖apk 📲
✔️ b86c28f #23 2024-03-07 09:48:55 ~12 min ios 📱ipa 📲
Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ cc45a8c #24 2024-03-12 05:37:05 ~7 min android-e2e 🤖apk 📲
✔️ cc45a8c #24 2024-03-12 05:37:10 ~7 min android 🤖apk 📲
✔️ cc45a8c #24 2024-03-12 05:40:57 ~11 min ios 📱ipa 📲
✔️ 38217ff #25 2024-03-12 07:09:39 ~6 min tests 📄log
✔️ 38217ff #25 2024-03-12 07:11:34 ~8 min android-e2e 🤖apk 📲
✔️ 38217ff #25 2024-03-12 07:11:42 ~8 min android 🤖apk 📲
✔️ 38217ff #25 2024-03-12 07:15:06 ~11 min ios 📱ipa 📲

@Parveshdhull Parveshdhull self-assigned this Feb 27, 2024
@Parveshdhull Parveshdhull force-pushed the feat/banner-test-net branch 10 times, most recently from 909435d to f5153d7 Compare March 3, 2024 12:52
@Parveshdhull Parveshdhull changed the title [WIP]: Implement alert banner Implement alert banner Mar 3, 2024
@Parveshdhull Parveshdhull marked this pull request as ready for review March 3, 2024 12:57
@Parveshdhull Parveshdhull moved this from REVIEW to E2E Tests in Pipeline for QA Mar 4, 2024
Copy link
Member

@flexsurfer flexsurfer left a comment

Choose a reason for hiding this comment

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

what a masterpiece!

@status-im-auto
Copy link
Member

96% of end-end tests have passed

Total executed tests: 48
Failed tests: 1
Expected to fail tests: 1
Passed tests: 46
IDs of failed tests: 702957 
IDs of expected to fail tests: 703503 

Failed tests (1)

Click to expand
  • Rerun failed tests

  • Class TestActivityMultipleDevicePRTwo:

    1. test_activity_center_mentions, id: 702957

    Device 2: Tap on found: SendMessageButton
    # STEP: Checking unread indicators

    activity_center/test_activity_center.py:424: in test_activity_center_mentions
        self.home_1.notifications_unread_badge.wait_for_visibility_of_element(120)
    ../views/base_element.py:147: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 1: BaseElement by accessibility id:`activity-center-unread-count` is not found on the screen after wait_for_visibility_of_element
    



    Device sessions

    Expected to fail tests (1)

    Click to expand

    Class TestCommunityOneDeviceMerged:

    1. test_community_discovery, id: 703503

    Test is not run, e2e blocker  
    

    [[reason: [NOTRUN] Curated communities not loading, https://github.com//issues/17852]]

    Passed tests (46)

    Click to expand

    Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:

    1. test_1_1_chat_delete_via_long_press_relogin, id: 702784
    Device sessions

    2. test_1_1_chat_is_shown_message_sent_delivered_from_offline, id: 702783
    Device sessions

    3. test_1_1_chat_mute_chat, id: 703496
    Device sessions

    Class TestActivityMultipleDevicePRTwo:

    1. test_activity_center_admin_notification_accept_swipe, id: 702958
    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_mentions_push_notification, id: 702786
    Device sessions

    4. test_community_leave, id: 702845
    Device sessions

    5. test_community_join_when_node_owner_offline, id: 703629
    Device sessions

    Class TestGroupChatMultipleDeviceMergedNewUI:

    1. test_group_chat_pin_messages, id: 702732
    Device sessions

    2. test_group_chat_mute_chat, id: 703495
    Device sessions

    3. test_group_chat_send_image_save_and_share, id: 703297
    Device sessions

    4. test_group_chat_reactions, id: 703202
    Device sessions

    5. test_group_chat_join_send_text_messages_push, id: 702807
    Device sessions

    6. test_group_chat_offline_pn, id: 702808
    Device sessions

    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 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_mark_all_messages_as_read, id: 703086
    Device sessions

    5. test_community_contact_block_unblock_offline, id: 702894
    Device sessions

    6. test_community_edit_delete_message_when_offline, id: 704615
    Device sessions

    7. test_community_message_delete, id: 702839
    Device sessions

    8. test_community_message_send_check_timestamps_sender_username, id: 702838
    Device sessions

    9. test_community_links_with_previews_github_youtube_twitter_gif_send_enable, id: 702844
    Device sessions

    10. test_community_message_edit, id: 702843
    Device sessions

    11. test_community_unread_messages_badge, id: 702841
    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_pin_messages, id: 702731
    Device sessions

    8. test_1_1_chat_message_reaction, id: 702730
    Device sessions

    Class TestDeepLinksOneDevice:

    1. test_links_open_universal_links_from_chat, id: 704613
    Device sessions

    2. test_links_deep_links, id: 702775
    Device sessions

    Class TestActivityCenterContactRequestMultipleDevicePR:

    1. test_add_contact_field_validation, id: 702777
    Device sessions

    2. test_activity_center_contact_request_accept_swipe_mark_all_as_read, id: 702851
    Device sessions

    3. test_activity_center_contact_request_decline, id: 702850
    Device sessions

    @seanstrom
    Copy link
    Member

    🤩 Looking good! Thanks for setting this up 🙏

    I do have a couple questions about some of the details, the main ones are:

    • Why use react-native-hole-view? I think it's used here because it can support click through, but I'm wondering if it's needed for another reason. Based on the code it seems like we could implement this without hole-view, is that true or is it needed for some other functionality?
    • What kinds of things could be affected by introducing the banners? I initially thought it would be stuff that relies on the top safe-area of the app, but it seems like it's mainly things that render outside the default navigation/screen layouts. Is that true?
      • So far it seems like bottom-sheets is the main thing that would be affected. Are floating action buttons like jump-to affected, or are those different in some way?

    Copy link
    Member

    @smohamedjavid smohamedjavid left a comment

    Choose a reason for hiding this comment

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

    Quality work! @Parveshdhull 🙌

    src/status_im/navigation/core.cljs Outdated Show resolved Hide resolved
    error-banner (:error banners)
    safe-area-top (safe-area/get-top)]
    [hole-view/hole-view
    {:style {:background-color colors/neutral-100}
    Copy link
    Member

    Choose a reason for hiding this comment

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

    Not sure we should set this color permanently. Maybe we should check how it looks in light mode.

    Copy link
    Member Author

    Choose a reason for hiding this comment

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

    Thank you for review Javid, I discussed this with mario and he mentioned alert banner will always use dark theme.

    Copy link
    Member

    Choose a reason for hiding this comment

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

    Great! 🙌

    Copy link
    Member

    Choose a reason for hiding this comment

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

    In that case, this will affect the color of the status bar. Correct me if I'm wrong.

    Copy link
    Member Author

    Choose a reason for hiding this comment

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

    In that case, this will affect the color of the status bar. Correct me if I'm wrong.

    Thank you very much for highlighting this. I will keep this in mind while working for status-bar color implementation for #19072

    src/status_im/common/alert_banner/view.cljs Outdated Show resolved Hide resolved
    @Parveshdhull
    Copy link
    Member Author

    Hi @seanstrom,
    Thank you for checking out the PR.

    Based on the code it seems like we could implement this without hole-view, is that true or is it needed for some other functionality

    image
    It looks like we have bottom screen area with border radius. But this is not the case. Bottom screen is lower(z-axis) then banner. So with help of hole-view, banner is cut in a way to show whatever is below it.

    What kinds of things could be affected by introducing the banners? I initially thought it would be stuff that relies on the top safe-area of the app, but it seems like it's mainly things that render outside the default navigation/screen layouts. Is that true?

    Yes, banners are not part of the screen. They are shown over all components.

    Overlays are used to layout content on top of all other layout hierarchies, while fitting the screen bounds
    https://wix.github.io/react-native-navigation/docs/overlay

    So far it seems like bottom-sheets is the main thing that would be affected. Are floating action buttons like jump-to affected, or are those different in some way?

    I don't think they are affected 🤔

    @seanstrom
    Copy link
    Member

    @Parveshdhull Thanks for the explanation, makes sense to me ✅
    The use of hole-view is very cool, well done!

    About the float action buttons, I suppose if their positioning is relative to the screen, then it should be okay as long as the screen dimensions are managed like they are in this PR (?) 🤔

    src/status_im/common/alert_banner/events.cljs Outdated Show resolved Hide resolved
    src/status_im/common/alert_banner/style.cljs Outdated Show resolved Hide resolved
    src/status_im/common/alert_banner/view.cljs Outdated Show resolved Hide resolved
    src/status_im/common/alert_banner/view.cljs Outdated Show resolved Hide resolved
    src/status_im/common/alert_banner/view.cljs Outdated Show resolved Hide resolved
    @mariia-skrypnyk mariia-skrypnyk moved this from E2E Tests to IN TESTING in Pipeline for QA Mar 7, 2024
    @mariia-skrypnyk
    Copy link

    Hi @Parveshdhull !

    Thanks fro your PR!
    I've tested both plaforms but see no banner.

    Does my steps correct?

    1. Login
    2. Go to Profile -> Advanced -> Testnet mode

    Also tried Goerli mode but it didn't helped.

    video_2024-03-07_12-34-06.mp4

    @mariia-skrypnyk mariia-skrypnyk self-assigned this Mar 7, 2024
    @Parveshdhull
    Copy link
    Member Author

    Hi @mariia-skrypnyk,

    Thank you very much for taking PR in testing.

    PR only implements alert banner feature, but we are not yet using it.

    For checking out/preview the feature, please use these steps

    Settings -> Legacy settings -> Status IM components -> banner - > alert banner preview

    Testing notes

    • As implementation of this feature makes changes in navigation related code, Please lightly test PR for navigation related issues. (Simple screens like, settings and bottom sheet screens etc. are not broken)
    • Please let me know if after enabling this feature, there are any bugs and regressions
    • Please feel free to report if there are any polishing issues. I will try to address them in this PR, or we can do in follow up when we enable this feature.

    Manual testing is just a precautionary step to make sure merging this PR is safe.

    Thank you for pinging me, Sorry I forgot to update the description after completing this feature. Please feel free to ping if you have any more questions.

    @mariia-skrypnyk
    Copy link

    mariia-skrypnyk commented Mar 8, 2024

    Hi @mariia-skrypnyk,

    Thank you very much for taking PR in testing.

    PR only implements alert banner feature, but we are not yet using it.

    For checking out/preview the feature, please use these steps

    Settings -> Legacy settings -> Status IM components -> banner - > alert banner preview

    Testing notes

    • As implementation of this feature makes changes in navigation related code, Please lightly test PR for navigation related issues. (Simple screens like, settings and bottom sheet screens etc. are not broken)
    • Please let me know if after enabling this feature, there are any bugs and regressions
    • Please feel free to report if there are any polishing issues. I will try to address them in this PR, or we can do in follow up when we enable this feature.

    Manual testing is just a precautionary step to make sure merging this PR is safe.

    Thank you for pinging me, Sorry I forgot to update the description after completing this feature. Please feel free to ping if you have any more questions.

    Hi @Parveshdhull !

    Thanks for such a detailed description! It was very useful!

    I found some minor things:

    ISSUE 1: Titles are not fully visible

    Place A) Advanced screen

    IMG_7270.MP4

    Place B) Notification settings screen
    Screenshot 2024-03-08 at 15 15 31

    Place C) Appearance screen
    Screenshot 2024-03-08 at 15 15 21

    Issues exist on both iOS and Android platforms.
    I still checking your PR but for now that's all I've found.
    Thanks!

    @Parveshdhull
    Copy link
    Member Author

    Thank you for reporting these issues.

    As old screens are using native topBar, custom margin are not working.

    This is expected and we can't fix that. But fortunately we are no longer using native topBar in new UI. These screens are all legacy and will be reimplemented, So please ignore these scenarios.

    @mariia-skrypnyk
    Copy link

    Hi @Parveshdhull !

    Thanks fro your answer. This issues are all that I've found during testing your PR.
    Going to look at e2e result and let you know.

    @status-im-auto
    Copy link
    Member

    73% of end-end tests have passed

    Total executed tests: 48
    Failed tests: 12
    Expected to fail tests: 1
    Passed tests: 35
    
    IDs of failed tests: 702840,702894,703086,702731,702844,702841,702839,702838,704615,702859,702843,703194 
    
    IDs of expected to fail tests: 703503 
    

    Failed tests (12)

    Click to expand
  • Rerun failed tests

  • Class TestCommunityMultipleDeviceMerged:

    1. test_community_emoji_send_copy_paste_reply, id: 702840
    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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
    



    2. test_community_contact_block_unblock_offline, id: 702894

    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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
    



    3. test_community_mark_all_messages_as_read, id: 703086

    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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
    



    4. test_community_links_with_previews_github_youtube_twitter_gif_send_enable, id: 702844

    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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
    



    5. test_community_unread_messages_badge, id: 702841

    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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
    



    6. test_community_message_delete, id: 702839

    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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
    



    7. test_community_message_send_check_timestamps_sender_username, id: 702838

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

    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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

    8. test_community_edit_delete_message_when_offline, id: 704615

    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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
    



    9. test_community_one_image_send_reply, id: 702859

    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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
    



    10. test_community_message_edit, id: 702843

    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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
    



    11. test_community_several_images_send_reply, id: 703194

    Test setup failed: critical/chats/test_public_chat_browsing.py:322: in prepare_devices
        self.community_2.join_community()
    ../views/chat_view.py:444: in join_community
        self.community_status_joined.wait_for_visibility_of_element(60)
    ../views/base_element.py:147: 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
    



    Class TestOneToOneChatMultipleSharedDevicesNewUi:

    1. test_1_1_chat_pin_messages, id: 702731

    Device 1: Find Button by xpath: //*[@content-desc='pins-count']//android.widget.TextView
    Device 1: Find Button by xpath: //*[@content-desc='pins-count']//android.widget.TextView

    critical/chats/test_1_1_public_chats.py:195: in test_1_1_chat_pin_messages
        chat.pinned_messages_count.wait_for_element_text(text="2",
    ../views/base_element.py:190: in wait_for_element_text
        self.driver.fail(message if message else "`%s` is not equal to expected `%s` in %s sec" % (
    base_test_case.py:179: in fail
        pytest.fail('Device %s: %s' % (self.number, text))
     Device 1: Pinned messages count is not 2 as expected!
    



    Device sessions

    Expected to fail tests (1)

    Click to expand

    Class TestCommunityOneDeviceMerged:

    1. test_community_discovery, id: 703503

    Test is not run, e2e blocker  
    

    [[reason: [NOTRUN] Curated communities not loading, https://github.com//issues/17852]]

    Passed tests (35)

    Click to expand

    Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:

    1. test_1_1_chat_mute_chat, id: 703496
    Device sessions

    2. test_1_1_chat_is_shown_message_sent_delivered_from_offline, id: 702783
    Device sessions

    3. test_1_1_chat_delete_via_long_press_relogin, id: 702784
    Device sessions

    Class TestActivityMultipleDevicePRTwo:

    1. test_activity_center_admin_notification_accept_swipe, id: 702958
    Device sessions

    2. test_activity_center_mentions, id: 702957
    Device sessions

    Class TestCommunityOneDeviceMerged:

    1. test_community_copy_and_paste_message_in_chat_input, id: 702742
    Device sessions

    2. test_community_navigate_to_channel_when_relaunch, id: 702846
    Device sessions

    3. test_restore_multiaccount_with_waku_backup_remove_switch, id: 703133
    Device sessions

    4. test_community_undo_delete_message, id: 702869
    Device sessions

    5. test_community_mute_community_and_channel, id: 703382
    Device sessions

    Class TestActivityMultipleDevicePR:

    1. test_activity_center_reply_read_unread_delete_filter_swipe, id: 702947
    Device sessions

    2. test_navigation_jump_to, id: 702936
    Device sessions

    Class TestCommunityMultipleDeviceMergedTwo:

    1. test_community_leave, id: 702845
    Device sessions

    2. test_community_mentions_push_notification, id: 702786
    Device sessions

    3. test_community_markdown_support, id: 702809
    Device sessions

    4. test_community_hashtag_links_to_community_channels, id: 702948
    Device sessions

    5. test_community_join_when_node_owner_offline, id: 703629
    Device sessions

    Class TestOneToOneChatMultipleSharedDevicesNewUi:

    1. test_1_1_chat_edit_message, id: 702855
    Device sessions

    2. test_1_1_chat_message_reaction, id: 702730
    Device sessions

    3. test_1_1_chat_non_latin_messages_stack_update_profile_photo, id: 702745
    Device sessions

    4. test_1_1_chat_text_message_delete_push_disappear, id: 702733
    Device sessions

    5. test_1_1_chat_push_emoji, id: 702813
    Device sessions

    6. test_1_1_chat_emoji_send_reply_and_open_link, id: 702782
    Device sessions

    7. test_1_1_chat_send_image_save_and_share, id: 703391
    Device sessions

    Class TestDeepLinksOneDevice:

    1. test_links_deep_links, id: 702775
    Device sessions

    2. test_links_open_universal_links_from_chat, id: 704613
    Device sessions

    Class TestGroupChatMultipleDeviceMergedNewUI:

    1. test_group_chat_reactions, id: 703202
    Device sessions

    2. test_group_chat_join_send_text_messages_push, id: 702807
    Device sessions

    3. test_group_chat_offline_pn, id: 702808
    Device sessions

    4. test_group_chat_pin_messages, id: 702732
    Device sessions

    5. test_group_chat_send_image_save_and_share, id: 703297
    Device sessions

    6. test_group_chat_mute_chat, id: 703495
    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

    3. test_add_contact_field_validation, id: 702777
    Device sessions

    @mariia-skrypnyk
    Copy link

    Hi @Parveshdhull !

    PR can be merged.
    Failed test are not related to your PR.

    @Parveshdhull Parveshdhull merged commit 604e232 into develop Mar 12, 2024
    6 checks passed
    Pipeline for QA automation moved this from MERGE to DONE Mar 12, 2024
    @Parveshdhull Parveshdhull deleted the feat/banner-test-net branch March 12, 2024 08:33
    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.

    Research banner implementation using navigation overlays
    7 participants