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

scan watched address #17829

Merged
merged 1 commit into from
Nov 20, 2023
Merged

scan watched address #17829

merged 1 commit into from
Nov 20, 2023

Conversation

J-Son89
Copy link
Contributor

@J-Son89 J-Son89 commented Nov 6, 2023

fixes #17808

fixes #17807

This pr fixes two issues.

  1. allow user to scan address on watch only flows

  2. adjust background color of emoji picker (account avatar) on create watch only account page ->

Also I adjusted copy from "watch address" subtitle to "Watched address" as pointed out in the demo by designers 👍

Test Notes:
make sure to create a new user when testing.
this does not add the ability to create a watch only flow - that will be added later.

trim.B55E575A-CC47-45BB-B5A8-F256556EC7CA.MOV

@status-im-auto
Copy link
Member

status-im-auto commented Nov 6, 2023

Jenkins Builds

Click to see older builds (51)
Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ df9c2ee #1 2023-11-06 12:07:15 ~5 min android 🤖apk 📲
✔️ df9c2ee #1 2023-11-06 12:08:26 ~6 min ios 📱ipa 📲
✔️ df9c2ee #1 2023-11-06 12:08:52 ~7 min android-e2e 🤖apk 📲
✔️ df9c2ee #1 2023-11-06 12:11:13 ~9 min tests 📄log
✔️ e6ff5fb #2 2023-11-08 18:53:16 ~6 min android-e2e 🤖apk 📲
✔️ e6ff5fb #2 2023-11-08 18:56:27 ~9 min android 🤖apk 📲
✔️ e6ff5fb #2 2023-11-08 18:56:49 ~9 min tests 📄log
✔️ e6ff5fb #2 2023-11-08 18:57:21 ~10 min ios 📱ipa 📲
9943f31 #3 2023-11-09 13:50:01 ~5 min tests 📄log
✔️ 9943f31 #3 2023-11-09 13:51:29 ~6 min android-e2e 🤖apk 📲
✔️ 9943f31 #3 2023-11-09 13:52:51 ~8 min android 🤖apk 📲
✔️ 9943f31 #3 2023-11-09 13:57:27 ~12 min ios 📱ipa 📲
✔️ 8a7a14c #4 2023-11-09 17:28:21 ~5 min android-e2e 🤖apk 📲
✔️ 8a7a14c #4 2023-11-09 17:28:28 ~5 min android 🤖apk 📲
✔️ 8a7a14c #4 2023-11-09 17:31:12 ~8 min tests 📄log
✔️ 8a7a14c #4 2023-11-09 17:33:02 ~10 min ios 📱ipa 📲
✔️ 74a472f #5 2023-11-10 14:44:12 ~5 min ios 📱ipa 📲
✔️ 74a472f #5 2023-11-10 14:45:06 ~6 min android-e2e 🤖apk 📲
✔️ 74a472f #5 2023-11-10 14:45:15 ~6 min android 🤖apk 📲
✔️ 74a472f #5 2023-11-10 14:47:27 ~8 min tests 📄log
✔️ 77f0861 #6 2023-11-10 14:59:36 ~6 min ios 📱ipa 📲
✔️ 77f0861 #6 2023-11-10 15:01:33 ~8 min tests 📄log
✔️ 77f0861 #6 2023-11-10 15:03:38 ~10 min android 🤖apk 📲
✔️ 77f0861 #6 2023-11-10 15:03:44 ~10 min android-e2e 🤖apk 📲
✔️ 8d87064 #7 2023-11-13 15:23:48 ~5 min ios 📱ipa 📲
✔️ 8d87064 #7 2023-11-13 15:24:19 ~5 min android-e2e 🤖apk 📲
✔️ 8d87064 #7 2023-11-13 15:27:35 ~9 min android 🤖apk 📲
✔️ 8d87064 #7 2023-11-13 15:27:38 ~9 min tests 📄log
8370c94 #8 2023-11-15 10:15:23 ~4 min tests 📄log
✔️ 8370c94 #8 2023-11-15 10:19:04 ~7 min android-e2e 🤖apk 📲
✔️ 8370c94 #8 2023-11-15 10:19:53 ~8 min android 🤖apk 📲
✔️ a7ae152 #10 2023-11-15 10:29:58 ~6 min android-e2e 🤖apk 📲
✔️ a7ae152 #9 2023-11-15 10:30:01 ~6 min ios 📱ipa 📲
✔️ a7ae152 #10 2023-11-15 10:30:01 ~6 min android 🤖apk 📲
✔️ a7ae152 #9 2023-11-15 10:33:39 ~10 min tests 📄log
8cbc993 #10 2023-11-15 17:10:43 ~2 min tests 📄log
✔️ 8cbc993 #10 2023-11-15 17:13:37 ~5 min ios 📱ipa 📲
✔️ 8cbc993 #11 2023-11-15 17:14:10 ~5 min android-e2e 🤖apk 📲
✔️ 8cbc993 #11 2023-11-15 17:14:48 ~6 min android 🤖apk 📲
✔️ 811abc7 #12 2023-11-15 17:22:11 ~5 min android 🤖apk 📲
✔️ 811abc7 #12 2023-11-15 17:25:26 ~8 min android-e2e 🤖apk 📲
✔️ 811abc7 #11 2023-11-15 17:25:33 ~9 min tests 📄log
✔️ 811abc7 #11 2023-11-15 17:27:19 ~10 min ios 📱ipa 📲
✔️ 0abe93f #12 2023-11-15 17:35:02 ~6 min ios 📱ipa 📲
✔️ 0abe93f #13 2023-11-15 17:38:34 ~10 min android-e2e 🤖apk 📲
✔️ 0abe93f #13 2023-11-15 17:38:38 ~10 min android 🤖apk 📲
✔️ 0abe93f #12 2023-11-15 17:38:43 ~10 min tests 📄log
✔️ 89fa43c #13 2023-11-17 13:47:48 ~5 min ios 📱ipa 📲
✔️ 89fa43c #14 2023-11-17 13:49:58 ~7 min android-e2e 🤖apk 📲
✔️ 89fa43c #14 2023-11-17 13:51:46 ~9 min android 🤖apk 📲
✔️ 89fa43c #13 2023-11-17 13:55:55 ~13 min tests 📄log
Commit #️⃣ Finished (UTC) Duration Platform Result
cddd7b5 #15 2023-11-19 20:27:42 ~2 min tests 📄log
✔️ cddd7b5 #16 2023-11-19 20:31:37 ~6 min android 🤖apk 📲
✔️ cddd7b5 #16 2023-11-19 20:31:38 ~6 min android-e2e 🤖apk 📲
✔️ cddd7b5 #15 2023-11-19 20:31:38 ~6 min ios 📱ipa 📲
✔️ e181d62 #17 2023-11-20 00:21:02 ~6 min android 🤖apk 📲
✔️ e181d62 #16 2023-11-20 00:21:17 ~6 min ios 📱ipa 📲
✔️ e181d62 #17 2023-11-20 00:23:16 ~8 min android-e2e 🤖apk 📲
✔️ e181d62 #16 2023-11-20 00:25:38 ~10 min tests 📄log

@J-Son89 J-Son89 changed the title Jc/scan watched address scan watched address Nov 8, 2023
@J-Son89 J-Son89 marked this pull request as ready for review November 8, 2023 18:47
@@ -1,4 +1,4 @@
(ns status-im2.contexts.wallet.add-watch-only-account.views
(ns status-im2.contexts.wallet.add-watch-only-account.view
Copy link
Contributor Author

Choose a reason for hiding this comment

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

aligning with best practices

@@ -36,7 +36,7 @@
{:customization-color account-color
:size 80
:emoji account-emoji
:type :default}]
:type (if watch-only? :watch-only :default)}]
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is the fix for: #17807

Copy link
Member

Choose a reason for hiding this comment

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

🚀

[utils.i18n :as i18n]
[utils.re-frame :as rf]))

(defn view-internal
(defn- address-input
[input-value input-focused?]
Copy link
Contributor Author

Choose a reason for hiding this comment

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

similar code to send scan address, most pieces here are reusable so I just copied the relevant pieces over to avoid coupling the send and watch only scanners.

[]
(let [top (safe-area/get-top)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

there was excess margin-top here

@@ -248,8 +248,8 @@
:options {:insets {:top? true}}
:component wallet-accounts/view}

{:name :address-to-watch-edit
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I found "edit" to be a bit misleading. We have "edit" account and so I did not want to confuse with that. here we are creating (or adding) the watch only account.

Copy link
Contributor

@OmarBasem OmarBasem Nov 9, 2023

Choose a reason for hiding this comment

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

I am working on an issue #17806 related to address watch, and I was also doing changes to the naming :) I pushed my PR to show the changes I made to avoid conflicts: https://github.com/status-im/status-mobile/pull/17859/files

I renamed select-address-to-watch to add-address-to-watch (to match the screen title) and moved add-watch-only-account under add-address-to-watch namespace and renamed it to edit-address (and screen name edit-addres-to-watch). I think that makes it clearer that the editing is for the watch address.

Also, we can use the word confirm instead of edit

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure I'll copy your changes, thanks for the heads up! 🙂

Copy link
Contributor

Choose a reason for hiding this comment

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

Renamed it to confirm-address. And PR is ready for review #17859 👍

@@ -36,7 +36,7 @@
{:customization-color account-color
:size 80
:emoji account-emoji
:type :default}]
:type (if watch-only? :watch-only :default)}]
Copy link
Member

Choose a reason for hiding this comment

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

🚀

(defn view-internal
(defn- address-input
[input-value input-focused?]
(fn []
Copy link
Member

Choose a reason for hiding this comment

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

I guess we can remove this (fn []) as we don't have any atoms.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sure I'll take a look at removing that.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, that's true, the fn [] is not needed.

Actually, this (fn[]) will cause problems with rerenders.

If input-value or input-focused? change, the body of the function will not be re executed, and if the component rerenders (e.g. because a sub changes), input-value and input-focused will have the value they had when the component mounted, not the current one

input-value (reagent/atom "")
customization-color (rf/sub [:profile/customization-color])]
input-focused? (reagent/atom false)]
Copy link
Member

Choose a reason for hiding this comment

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

I noticed that the input-focused? value is not used inside the address-input. Are we planning to use it in future?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

whoops, I was being a bit blind there 😓 I'm going to remove this, and actually @briansztamfater I think on the send address screens we eventually should be using this as it will (should) handle that behaviour
#17737

Copy link
Contributor Author

@J-Son89 J-Son89 Nov 8, 2023

Choose a reason for hiding this comment

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

will use the same approach on this page when that pr is merged too 👍

(fn []
(rn/use-effect (fn [] #(rf/dispatch [:wallet/clean-scanned-address])))
Copy link
Member

Choose a reason for hiding this comment

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

I believe we can dispatch this clean-up event (before the let) prior to UI mount without the use-effect (and the functional component [:f>] wrapping). Just like we did on the wallet home page for collectables.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sure, I'll do that 👍

Copy link
Contributor

@ulisesmac ulisesmac left a comment

Choose a reason for hiding this comment

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

Just small comments! 💯

(defn view-internal
(defn- address-input
[input-value input-focused?]
(fn []
Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, that's true, the fn [] is not needed.

Actually, this (fn[]) will cause problems with rerenders.

If input-value or input-focused? change, the body of the function will not be re executed, and if the component rerenders (e.g. because a sub changes), input-value and input-focused will have the value they had when the component mounted, not the current one

@J-Son89 J-Son89 force-pushed the jc/scan-watched-address branch 2 times, most recently from 9943f31 to 8a7a14c Compare November 9, 2023 17:22
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.

Nice work! 🚀


(defn view
[]
[:f> f-view])
Copy link
Member

Choose a reason for hiding this comment

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

We can move all code from the f-view to view and remove the [:f>] as we don't use any react hooks inside this page.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point!

Copy link
Member

@briansztamfater briansztamfater left a comment

Choose a reason for hiding this comment

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

LGTM!

Comment on lines 49 to 50
[rn/view
{:style {:flex 1}}
Copy link
Member

Choose a reason for hiding this comment

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

Super minor, this can be in the same line

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will adjust!

@J-Son89
Copy link
Contributor Author

J-Son89 commented Nov 9, 2023

LGTM!

Np, was easy to reuse the code you added for this 💪🏼

@J-Son89 J-Son89 force-pushed the jc/scan-watched-address branch 2 times, most recently from 74a472f to 77f0861 Compare November 10, 2023 14:53
@VolodLytvynenko
Copy link
Contributor

Hi @J-Son89 thank you for the fixes.
Issue 1 is fixed partially

Actual result:

  • Text 'ETH address or ENS name' is not shown above the textbox
  • "Enter any ETH address or ENS name" text should be shown upper and as per design
    image

Expected result:

How it shown on design and latest nightly:
image
https://www.figma.com/file/HKncH4wnDwZDAhc4AryK8Y/Wallet-for-Mobile?type=design&node-id=1-111913&mode=design&t=SXYM8uGR119rbQvX-0

@VolodLytvynenko
Copy link
Contributor

VolodLytvynenko commented Nov 17, 2023

ISSUE 8: Incorrect address added to ETH address textbox after scanning QR Code

Steps:

  1. Generate an ETH QR code (from Status or Metamask).
  2. Scan the QR code by starting the camera from the bottom part of the QR.
  3. Observe the result.

Actual result:

The invalid address is added into ETH textbox

video.mp4

Expected result:

The valid address contained in the QR should be added into the ETH textbox.

Device:

Pixel 7a, Android 13

Logs:

Status-debug-logs (1).zip

Additional info:

Currently, the issue reproduces randomly, occurring only when quickly initiating the camera hover from the QR's edge

@VolodLytvynenko
Copy link
Contributor

@J-Son89 But it's alright if this issue gets fixed separately. It might not be within the scope of this PR. Please inform me if it will be addressed in this PR.

ISSUE 9: Random color picker selected after tapping 'Continue' during watch only address creation

Steps:

  1. Scan valid QR
  2. Tap 'Continue'
  3. Check selected color picker

Actual result:

The random color picker is selected

color_picker.mp4

Expected result:

The default selection should be the dark blue (first color picker).

@J-Son89
Copy link
Contributor Author

J-Son89 commented Nov 17, 2023

Thank @VolodLytvynenko - I will address these. Actually the random color is expected behaviour.
When creating a new wallet account or new watch only account the user should get a random color and a random emoji (unique combination)

The only account which needs to to be same as the user color is the initial account but this can be adjusted afterwards. The initial account emoji is also random.
Cc @OmarBasem to confirm

I'll ask designers to add a note in the figma file with this!

@OmarBasem
Copy link
Contributor

Thank @VolodLytvynenko - I will address these. Actually the random color is expected behaviour. When creating a new wallet account or new watch only account the user should get a random color and a random emoji (unique combination)

The only account which needs to to be same as the user color is the initial account but this can be adjusted afterwards. The initial account emoji is also random. Cc @OmarBasem to confirm

I'll ask designers to add a note in the figma file with this!

That's correct! 👍

@J-Son89
Copy link
Contributor Author

J-Son89 commented Nov 17, 2023

Hi @J-Son89 thank you for the fixes. Issue 1 is fixed partially

Actual result:

  • Text 'ETH address or ENS name' is not shown above the textbox
  • "Enter any ETH address or ENS name" text should be shown upper and as per design
    image

Expected result:

How it shown on design and latest nightly: image https://www.figma.com/file/HKncH4wnDwZDAhc4AryK8Y/Wallet-for-Mobile?type=design&node-id=1-111913&mode=design&t=SXYM8uGR119rbQvX-0

Fixed now, and verified on ios build alongside figma designs 👍

@status-im-auto
Copy link
Member

42% of end-end tests have passed

Total executed tests: 45
Failed tests: 24
Expected to fail tests: 2
Passed tests: 19
IDs of failed tests: 702782,703194,702859,703133,702957,702851,702840,703495,703086,702894,702745,703297,703503,703202,702839,702947,702838,702844,702843,702807,702808,702730,702958,702841 
IDs of expected to fail tests: 702732,702731 

Failed tests (24)

Click to expand
  • Rerun failed tests

  • Class TestCommunityOneDeviceMerged:

    1. test_restore_multiaccount_with_waku_backup_remove_switch, id: 703133

    Device 1: Find `Button` by `accessibility id`: `show-profiles`
    Device 1: Tap on found: Button

    critical/chats/test_public_chat_browsing.py:274: in test_restore_multiaccount_with_waku_backup_remove_switch
        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))]))
     zQ3...rLSpUs was not restored as a contact from waku backup!
    



    Device sessions

    2. test_community_discovery, id: 703503

    Device 1: Find Button by accessibility id: communities-home-discover-card
    Device 1: Tap on found: Button

    critical/chats/test_public_chat_browsing.py:40: in test_community_discovery
        self.home.community_card_item.wait_for_visibility_of_element(30)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 1: BaseElement by accessibility id:`community-card-item` is not found on the screen after wait_for_visibility_of_element
    



    Device sessions

    Class TestOneToOneChatMultipleSharedDevicesNewUi:

    1. test_1_1_chat_emoji_send_reply_and_open_link, id: 702782

    Device 2: Long press on ChatElementByText until expected element is shown
    Device 2: Find Button by accessibility id: reaction-thumbs-up

    critical/chats/test_1_1_public_chats.py:155: in test_1_1_chat_emoji_send_reply_and_open_link
        self.chat_2.set_reaction(url_message)
    ../views/chat_view.py:1077: in set_reaction
        element.click()
    ../views/base_element.py:90: in click
        self.find_element().click()
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 2: Button by accessibility id: `reaction-thumbs-up` 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

    2. test_1_1_chat_non_latin_messages_stack_update_profile_photo, id: 702745

    Device 2: Find MemberPhoto by xpath: //*[starts-with(@text,'profile_photo')]/ancestor::android.view.ViewGroup[@content-desc='chat-item']//*[@content-desc='user-avatar']
    Device 2: Image differs from template to 6.797401577818627 percents

    critical/chats/test_1_1_public_chats.py:314: in test_1_1_chat_non_latin_messages_stack_update_profile_photo
        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 with text 'hello' was not received
    E    Message with text '¿Cómo estás tu año?' was not received
    E    Message with text 'ё, доброго вечерочка' was not received
    E    Message with text '®	æ ç ♥' was not received
    



    Device sessions

    3. test_1_1_chat_message_reaction, id: 702730

    Device 2: Wait for text element EmojisNumber to be equal to 1
    Device 2: Find EmojisNumber by xpath: //*[starts-with(@text,'Message sender')]/ancestor::android.view.ViewGroup[@content-desc='chat-item']/../..//*[@content-desc='emoji-reaction-2']/android.widget.TextView

    critical/chats/test_1_1_public_chats.py:62: in test_1_1_chat_message_reaction
        message_receiver.emojis_below_message(emoji="thumbs-up").wait_for_element_text(1, 90)
    ../views/base_element.py:172: in wait_for_element_text
        element_text = self.find_element().text.strip()
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 2: EmojisNumber by xpath: `//*[starts-with(@text,'Message sender')]/ancestor::android.view.ViewGroup[@content-desc='chat-item']/../..//*[@content-desc='emoji-reaction-2']/android.widget.TextView` 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

    Class TestActivityMultipleDevicePRTwo:

    1. test_activity_center_mentions, id: 702957

    Device 2: Looking for chat: 'general'
    Device 2: Click until ChatMessageInput by accessibility id: chat-message-input will be presented

    Test setup failed: activity_center/test_activity_center.py:399: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element
    



    Device sessions

    2. test_activity_center_admin_notification_accept_swipe, id: 702958

    Test setup failed: activity_center/test_activity_center.py:399: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element
    



    Class TestGroupChatMultipleDeviceMergedNewUI:

    1. test_group_chat_mute_chat, id: 703495

    Test setup failed: ../views/home_view.py:382: in handle_contact_request
        chat_element.accept_contact_request()
    ../views/home_view.py:150: in accept_contact_request
        self.handle_cr("accept-contact-request")
    ../views/home_view.py:147: in handle_cr
        ).wait_for_rendering_ended_and_click()
    ../views/base_element.py:155: in wait_for_rendering_ended_and_click
        self.click()
    ../views/base_element.py:90: in click
        self.find_element().click()
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 3: Button by xpath: `//*[contains(@text, 'user admin')]/ancestor::*[@content-desc='activity']/*[@content-desc="accept-contact-request"]` 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
    
    During handling of the above exception, another exception occurred:
    critical/chats/test_group_chat.py:54: in prepare_devices
        self.loop.run_until_complete(
    /usr/lib/python3.10/asyncio/base_events.py:646: in run_until_complete
        return future.result()
    __init__.py:44: in run_in_parallel
        returns.append(await k)
    /usr/lib/python3.10/concurrent/futures/thread.py:58: in run
        result = self.fn(*self.args, **self.kwargs)
    ../views/home_view.py:392: in handle_contact_request
        self.driver.fail("No contact request received from %s" % username)
    base_test_case.py:179: in fail
        pytest.fail('Device %s: %s' % (self.number, text))
    E   Failed: Device 3: No contact request received from user admin
    



    2. test_group_chat_send_image_save_and_share, id: 703297

    Test setup failed: ../views/home_view.py:382: in handle_contact_request
        chat_element.accept_contact_request()
    ../views/home_view.py:150: in accept_contact_request
        self.handle_cr("accept-contact-request")
    ../views/home_view.py:147: in handle_cr
        ).wait_for_rendering_ended_and_click()
    ../views/base_element.py:155: in wait_for_rendering_ended_and_click
        self.click()
    ../views/base_element.py:90: in click
        self.find_element().click()
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 3: Button by xpath: `//*[contains(@text, 'user admin')]/ancestor::*[@content-desc='activity']/*[@content-desc="accept-contact-request"]` 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
    
    During handling of the above exception, another exception occurred:
    critical/chats/test_group_chat.py:54: in prepare_devices
        self.loop.run_until_complete(
    /usr/lib/python3.10/asyncio/base_events.py:646: in run_until_complete
        return future.result()
    __init__.py:44: in run_in_parallel
        returns.append(await k)
    /usr/lib/python3.10/concurrent/futures/thread.py:58: in run
        result = self.fn(*self.args, **self.kwargs)
    ../views/home_view.py:392: in handle_contact_request
        self.driver.fail("No contact request received from %s" % username)
    base_test_case.py:179: in fail
        pytest.fail('Device %s: %s' % (self.number, text))
    E   Failed: Device 3: No contact request received from user admin
    



    3. test_group_chat_reactions, id: 703202

    Test setup failed: ../views/home_view.py:382: in handle_contact_request
        chat_element.accept_contact_request()
    ../views/home_view.py:150: in accept_contact_request
        self.handle_cr("accept-contact-request")
    ../views/home_view.py:147: in handle_cr
        ).wait_for_rendering_ended_and_click()
    ../views/base_element.py:155: in wait_for_rendering_ended_and_click
        self.click()
    ../views/base_element.py:90: in click
        self.find_element().click()
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 3: Button by xpath: `//*[contains(@text, 'user admin')]/ancestor::*[@content-desc='activity']/*[@content-desc="accept-contact-request"]` 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
    
    During handling of the above exception, another exception occurred:
    critical/chats/test_group_chat.py:54: in prepare_devices
        self.loop.run_until_complete(
    /usr/lib/python3.10/asyncio/base_events.py:646: in run_until_complete
        return future.result()
    __init__.py:44: in run_in_parallel
        returns.append(await k)
    /usr/lib/python3.10/concurrent/futures/thread.py:58: in run
        result = self.fn(*self.args, **self.kwargs)
    ../views/home_view.py:392: in handle_contact_request
        self.driver.fail("No contact request received from %s" % username)
    base_test_case.py:179: in fail
        pytest.fail('Device %s: %s' % (self.number, text))
    E   Failed: Device 3: No contact request received from user admin
    



    4. test_group_chat_join_send_text_messages_push, id: 702807

    Device 3: Tap on found: Button
    Device 3: Attempt 0 is successful clicking close-activity-center

    Test setup failed: ../views/home_view.py:382: in handle_contact_request
        chat_element.accept_contact_request()
    ../views/home_view.py:150: in accept_contact_request
        self.handle_cr("accept-contact-request")
    ../views/home_view.py:147: in handle_cr
        ).wait_for_rendering_ended_and_click()
    ../views/base_element.py:155: in wait_for_rendering_ended_and_click
        self.click()
    ../views/base_element.py:90: in click
        self.find_element().click()
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 3: Button by xpath: `//*[contains(@text, 'user admin')]/ancestor::*[@content-desc='activity']/*[@content-desc="accept-contact-request"]` 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
    
    During handling of the above exception, another exception occurred:
    critical/chats/test_group_chat.py:54: in prepare_devices
        self.loop.run_until_complete(
    /usr/lib/python3.10/asyncio/base_events.py:646: in run_until_complete
        return future.result()
    __init__.py:44: in run_in_parallel
        returns.append(await k)
    /usr/lib/python3.10/concurrent/futures/thread.py:58: in run
        result = self.fn(*self.args, **self.kwargs)
    ../views/home_view.py:392: in handle_contact_request
        self.driver.fail("No contact request received from %s" % username)
    base_test_case.py:179: in fail
        pytest.fail('Device %s: %s' % (self.number, text))
    E   Failed: Device 3: No contact request received from user admin
    



    Device sessions

    5. test_group_chat_offline_pn, id: 702808

    Test setup failed: ../views/home_view.py:382: in handle_contact_request
        chat_element.accept_contact_request()
    ../views/home_view.py:150: in accept_contact_request
        self.handle_cr("accept-contact-request")
    ../views/home_view.py:147: in handle_cr
        ).wait_for_rendering_ended_and_click()
    ../views/base_element.py:155: in wait_for_rendering_ended_and_click
        self.click()
    ../views/base_element.py:90: in click
        self.find_element().click()
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 3: Button by xpath: `//*[contains(@text, 'user admin')]/ancestor::*[@content-desc='activity']/*[@content-desc="accept-contact-request"]` 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
    
    During handling of the above exception, another exception occurred:
    critical/chats/test_group_chat.py:54: in prepare_devices
        self.loop.run_until_complete(
    /usr/lib/python3.10/asyncio/base_events.py:646: in run_until_complete
        return future.result()
    __init__.py:44: in run_in_parallel
        returns.append(await k)
    /usr/lib/python3.10/concurrent/futures/thread.py:58: in run
        result = self.fn(*self.args, **self.kwargs)
    ../views/home_view.py:392: in handle_contact_request
        self.driver.fail("No contact request received from %s" % username)
    base_test_case.py:179: in fail
        pytest.fail('Device %s: %s' % (self.number, text))
    E   Failed: Device 3: No contact request received from user admin 
    

    [[Data delivery issue]]

    Class TestCommunityMultipleDeviceMerged:

    1. test_community_several_images_send_reply, id: 703194

    Test setup failed: critical/chats/test_public_chat_browsing.py:323: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element
    



    2. test_community_one_image_send_reply, id: 702859

    Test setup failed: critical/chats/test_public_chat_browsing.py:323: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element
    



    3. test_community_emoji_send_copy_paste_reply, id: 702840

    Test setup failed: critical/chats/test_public_chat_browsing.py:323: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element
    



    4. test_community_mark_all_messages_as_read, id: 703086

    Test setup failed: critical/chats/test_public_chat_browsing.py:323: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element
    



    5. test_community_contact_block_unblock_offline, id: 702894

    Test setup failed: critical/chats/test_public_chat_browsing.py:323: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element 
    

    [[Message can be missed after unblock: https://github.com//issues/16873]]

    6. test_community_message_delete, id: 702839

    Test setup failed: critical/chats/test_public_chat_browsing.py:323: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` 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: Looking for chat: 'general'
    Device 2: Click until ChatMessageInput by accessibility id: chat-message-input will be presented

    Test setup failed: critical/chats/test_public_chat_browsing.py:323: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element
    



    Device sessions

    8. test_community_links_with_previews_github_youtube_twitter_gif_send_enable, id: 702844

    Test setup failed: critical/chats/test_public_chat_browsing.py:323: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element
    



    9. test_community_message_edit, id: 702843

    Test setup failed: critical/chats/test_public_chat_browsing.py:323: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element
    



    10. test_community_unread_messages_badge, id: 702841

    Test setup failed: critical/chats/test_public_chat_browsing.py:323: in prepare_devices
        self.channel_2.chat_message_input.wait_for_visibility_of_element(20)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 2: ChatMessageInput by accessibility id:`chat-message-input` is not found on the screen after wait_for_visibility_of_element
    



    Class TestActivityMultipleDevicePR:

    1. test_activity_center_reply_read_unread_delete_filter_swipe, id: 702947

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

    activity_center/test_activity_center.py:288: in test_activity_center_reply_read_unread_delete_filter_swipe
        self.home_1.notifications_unread_badge.wait_for_visibility_of_element(120)
    ../views/base_element.py:139: 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

    Class TestActivityCenterContactRequestMultipleDevicePR:

    1. test_activity_center_contact_request_accept_swipe_mark_all_as_read, id: 702851

    Device 1: Find ChatsTab by accessibility id: chats-stack-tab
    Device 1: Tap on found: ChatsTab

    activity_center/test_activity_center.py:108: in test_activity_center_contact_request_accept_swipe_mark_all_as_read
        self.home_1.notifications_unread_badge.wait_for_visibility_of_element(30)
    ../views/base_element.py:139: 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 (2)

    Click to expand

    Class TestGroupChatMultipleDeviceMergedNewUI:

    1. test_group_chat_pin_messages, id: 702732

    Test is not run, e2e blocker  
    

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

    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 (19)

    Click to expand

    Class TestCommunityOneDeviceMerged:

    1. test_community_copy_and_paste_message_in_chat_input, id: 702742
    Device sessions

    2. test_community_undo_delete_message, id: 702869
    Device sessions

    3. test_community_navigate_to_channel_when_relaunch, id: 702846
    Device sessions

    4. test_community_mute_community_and_channel, id: 703382
    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 TestOneToOneChatMultipleSharedDevicesNewUi:

    1. test_1_1_chat_text_message_delete_push_disappear, id: 702733
    Device sessions

    2. test_1_1_chat_push_emoji, id: 702813
    Device sessions

    3. test_1_1_chat_edit_message, id: 702855
    Device sessions

    4. test_1_1_chat_send_image_save_and_share, id: 703391
    Device sessions

    Class TestActivityMultipleDevicePR:

    1. test_navigation_jump_to, id: 702936
    Device sessions

    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 TestActivityCenterContactRequestMultipleDevicePR:

    1. test_add_contact_field_validation, id: 702777
    Device sessions

    2. test_activity_center_contact_request_decline, id: 702850
    Device sessions

    @status-im-auto
    Copy link
    Member

    84% of end-end tests have passed

    Total executed tests: 45
    Failed tests: 3
    Expected to fail tests: 4
    Passed tests: 38
    
    IDs of failed tests: 703133,703503,703629 
    
    IDs of expected to fail tests: 702732,702783,702731,702808 
    

    Failed tests (3)

    Click to expand
  • Rerun failed tests

  • Class TestCommunityOneDeviceMerged:

    1. test_restore_multiaccount_with_waku_backup_remove_switch, id: 703133

    Device 1: Find `Button` by `accessibility id`: `show-profiles`
    Device 1: Tap on found: Button

    critical/chats/test_public_chat_browsing.py:274: in test_restore_multiaccount_with_waku_backup_remove_switch
        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))]))
     zQ3...rLSpUs was not restored as a contact from waku backup!
    



    Device sessions

    2. test_community_discovery, id: 703503

    Device 1: Find Button by accessibility id: communities-home-discover-card
    Device 1: Tap on found: Button

    critical/chats/test_public_chat_browsing.py:40: in test_community_discovery
        self.home.community_card_item.wait_for_visibility_of_element(30)
    ../views/base_element.py:139: in wait_for_visibility_of_element
        raise TimeoutException(
     Device 1: BaseElement by accessibility id:`community-card-item` is not found on the screen after wait_for_visibility_of_element
    



    Device sessions

    Class TestCommunityMultipleDeviceMergedTwo:

    1. test_community_join_when_node_owner_offline, id: 703629

    Device 2: Looking for a message by text: open community
    Device 2: Find BaseElement by xpath: //*[starts-with(@text,'open community')]/ancestor::android.view.ViewGroup[@content-desc='chat-item']//*[@text='View']

    critical/chats/test_public_chat_browsing.py:1069: in test_community_join_when_node_owner_offline
        self.chat_2.chat_element_by_text(community_name).view_community_button.click()
    ../views/base_element.py:90: in click
        self.find_element().click()
    ../views/base_element.py:79: in find_element
        raise NoSuchElementException(
     Device 2: BaseElement by xpath: `//*[starts-with(@text,'open community')]/ancestor::android.view.ViewGroup[@content-desc='chat-item']//*[@text='View']` 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

    Expected to fail tests (4)

    Click to expand

    Class TestOneToOneChatMultipleSharedDevicesNewUi:

    1. test_1_1_chat_pin_messages, id: 702731

    Test is not run, e2e blocker  
    

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

    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_offline_pn, id: 702808

    Device 3: Looking for a message by text: message from old member
    Device 3: Looking for a message by text: message from new member

    critical/chats/test_group_chat.py:323: in test_group_chat_offline_pn
        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))]))
     Messages PN was not fetched from offline 
    

    [[Data delivery issue]]

    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:622: 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 status was not changed to Delivered, it's Sent after back up online! 
    

    [[Data delivery issue]]

    Device sessions

    Passed tests (38)

    Click to expand

    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

    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_message_delete, id: 702839
    Device sessions

    7. test_community_message_send_check_timestamps_sender_username, id: 702838
    Device sessions

    8. test_community_links_with_previews_github_youtube_twitter_gif_send_enable, id: 702844
    Device sessions

    9. test_community_message_edit, id: 702843
    Device sessions

    10. test_community_unread_messages_badge, id: 702841
    Device sessions

    Class TestCommunityOneDeviceMerged:

    1. test_community_copy_and_paste_message_in_chat_input, id: 702742
    Device sessions

    2. test_community_undo_delete_message, id: 702869
    Device sessions

    3. test_community_navigate_to_channel_when_relaunch, id: 702846
    Device sessions

    4. test_community_mute_community_and_channel, id: 703382
    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 TestGroupChatMultipleDeviceMergedNewUI:

    1. test_group_chat_mute_chat, id: 703495
    Device sessions

    2. test_group_chat_send_image_save_and_share, id: 703297
    Device sessions

    3. test_group_chat_reactions, id: 703202
    Device sessions

    4. test_group_chat_join_send_text_messages_push, id: 702807
    Device sessions

    Class TestActivityMultipleDevicePRTwo:

    1. test_activity_center_mentions, id: 702957
    Device sessions

    2. test_activity_center_admin_notification_accept_swipe, id: 702958
    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

    Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:

    1. test_1_1_chat_delete_via_long_press_relogin, id: 702784
    Device sessions

    2. test_1_1_chat_mute_chat, id: 703496
    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

    @VolodLytvynenko
    Copy link
    Contributor

    @J-Son89 J-Son89 merged commit 86c5505 into develop Nov 20, 2023
    6 checks passed
    @J-Son89 J-Son89 deleted the jc/scan-watched-address branch November 20, 2023 00:26
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    Archived in project
    Archived in project
    9 participants