Closed Parveshdhull closed 1 month ago
:grey_question: | Commit | :hash: | Finished (UTC) | Duration | Platform | Result |
---|---|---|---|---|---|---|
:heavy_check_mark: | 143c3c49 | #4 | 2024-10-24 13:46:34 | ~5 min | tests |
:page_facing_up:log |
:heavy_check_mark: | 143c3c49 | #4 | 2024-10-24 13:47:37 | ~6 min | android-e2e |
:robot:apk :calling: |
:heavy_check_mark: | 143c3c49 | #4 | 2024-10-24 13:50:13 | ~9 min | android |
:robot:apk :calling: |
:heavy_check_mark: | 143c3c49 | #4 | 2024-10-24 13:51:15 | ~10 min | ios |
:iphone:ipa :calling: |
:heavy_check_mark: | 57825dcf | #5 | 2024-10-28 19:17:48 | ~4 min | tests |
:page_facing_up:log |
:heavy_check_mark: | 57825dcf | #5 | 2024-10-28 19:21:13 | ~8 min | android |
:robot:apk :calling: |
:heavy_check_mark: | 57825dcf | #5 | 2024-10-28 19:22:13 | ~9 min | android-e2e |
:robot:apk :calling: |
:heavy_check_mark: | 57825dcf | #5 | 2024-10-28 19:22:32 | ~9 min | ios |
:iphone:ipa :calling: |
Total executed tests: 8
Failed tests: 2
Expected to fail tests: 0
Passed tests: 6
IDs of failed tests: 703133,702843
1. test_community_message_edit, id: 702843 |
``` Test setup failed: critical/chats/test_public_chat_browsing.py:350: in prepare_devices self.community_2.join_community() ../views/chat_view.py:420: in join_community self.join_button.wait_and_click(120) ../views/base_element.py:100: in wait_and_click self.wait_for_visibility_of_element(sec) ../views/base_element.py:147: in wait_for_visibility_of_element raise TimeoutException( Device 2: Button by accessibility id:`show-request-to-join-screen-button` is not found on the screen after wait_for_visibility_of_element ``` Device sessions Device 1: Device 2: |
1. test_restore_multiaccount_with_waku_backup_remove_switch, id: 703133 |
``` critical/chats/test_public_chat_browsing.py:240: in test_restore_multiaccount_with_waku_backup_remove_switch self.sign_in.show_profiles_button.wait_and_click() ../views/base_element.py:100: in wait_and_click self.wait_for_visibility_of_element(sec) ../views/base_element.py:147: in wait_for_visibility_of_element raise TimeoutException( Device 1: Button by accessibility id:`show-profiles` is not found on the screen after wait_for_visibility_of_element ``` Device sessions Device 1: |
1. test_wallet_send_asset_from_drawer, id: 727230 |
2. test_wallet_send_eth, id: 727229 |
1. test_community_copy_and_paste_message_in_chat_input, id: 702742 |
Device sessions Device 1: |
1. test_1_1_chat_non_latin_messages_stack_update_profile_photo, id: 702745 |
Device sessions Device 1: Device 2: |
1. test_wallet_add_remove_regular_account, id: 727231 |
2. test_wallet_balance_mainnet, id: 740490 |
Hi! If we improve our onboarding process, we might also consider improving the animation delay. Here’s how the onboarding currently looks on my emulator with and without the animation delay. (probably more faster on some devices)
https://github.com/user-attachments/assets/4938968f-ca9f-4951-91be-affe1d57333c
cc: @ilmotta @churik @flexsurfer
By the way, this isn’t critical, but I just wanted to raise this point. To me, It seems a bit inconsistent that in some areas we’re focused on saving milliseconds for performance, while in others we’re introducing delays of few seconds.
By the way, this isn’t critical, but I just wanted to raise this point. To me, It seems a bit inconsistent that in some areas we’re focused on saving milliseconds for performance, while in others we’re introducing delays of few seconds.
I took note of your feedback @Parveshdhull to consider in the mini-epic to simplify onboarding for the 2.32 release. There are still some details to align with designers and PL.
So I made 5 rounds of e2e in https://github.com/status-im/status-mobile/pull/21471 - I didn't face this issue.
And no regression from the PR as well.
I tested briefly account creation and sync on IOS - it works. We should merge and cherry pick this to the release branch, exceptional work @Parveshdhull - thank you!
this PR closes https://github.com/status-im/status-mobile/issues/21151 as well (hopefully!!!)
fixes https://github.com/status-im/status-mobile/issues/20806
Summary
Navigate to next screen once onboarding animation and account creation both are complete.
Note: If account creation fails, user will get stuck on loading screen.
Testing
Needs to adjust tests as per https://github.com/status-im/status-mobile/pull/21471
status: ready