[Onboarding - Stage 1] Onboarding Flow

Open MaciejSWM opened this issue 1 year ago • 54 comments

Details

In order to invoke the Onboarding Flow, replace a button of your choice in the app:

onPress={() => Navigation.navigate(ROUTES.ONBOARDING_PERSONAL_DETAILS)}

Or a direct invoke using URL: https://dev.new.expensify.com:8082/onboarding

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/351581 PROPOSAL:

Tests

Navigate to the onboarding flow by manually navigating to '/onboarding' or overwriting a button.
Input a name and a surname in the input fields, press continue button.
Click on any of the displayed options and press continue.
Verify that a video modal pops up with the app explaination video, if you're on desktop you should also get auto-navigated to the concierge report.
Verify that you've received the correct message in the concierge report (it depends on the purpose you've chosen).

[x] Verify that no errors appear in the JS console

Offline tests

Navigate to the onboarding flow by manually navigating to '/onboarding' or overwriting a button.
Input a name and a surname in the input fields, press continue button.
Click on any of the displayed options and press continue.
Instead of a video, the modal should display a lottie animation when in offline mode. The rest of the flow should stay the same.

QA Steps

Account creation -> Name + surname screen

Go to staging.new.expensify.com
Log in and navigate through Profile > About > Troubleshoot and press the 'Navigate' button next to Onboarding flow label
Verify the onboarding modal shows up
Verify you land on the Name + surname portion of the onboarding modal
Verify there's no 'X' to close the modal
Verify modal cannot be dismissed by clicking outside of it or by any other method
Verify refreshing the page does not dismiss the modal
Verify any input typed in the name and surname fields is kept between page refreshes
Verify clicking on Continue presents an error if either name or surname is empty
Verify " " (space) is a valid character to put in the name or surname field and it is treated as a valid name/surname (see top-level doc for explanation)
Verify clicking Continue takes you to the What do you want to do today? screen if Name + surname fields are correctly filled

Account creation -> Name + surname screen -> What do you want to do today? screen

Go to staging.new.expensify.com
Log in and navigate through Profile > About > Troubleshoot and press the 'Navigate' button next to Onboarding flow label
Fill in name and surname and hit Continue
Land on What do you want to do today? screen
Verify there's no 'X' to close the modal
Verify modal cannot be dismissed by clicking outside of it or by any other method
Verify refreshing the page does not dismiss the modal
Verify refreshing the page brings you back to the What do you want to do today? screen, as opposed to bringing you back to the Name + surname screen
Hitting Continue when no option is selected shows an error
Verify only a single option can be selected from multiple options presented
Verify chosen option is persisted between page refreshes
Verify pressing Back button navigates back to the Name + surname screen, and restores previously input name and surname

Account creation -> Onboarding modal completed -> Chats

Go to staging.new.expensify.com
Log in and navigate through Profile > About > Troubleshoot and press the 'Navigate' button next to Onboarding flow label
Fill in name and surname and hit Continue
Select any option in the What do you want to do today? Screen and hit Continue
Onboarding modal closes and two things happen almost simultaneously:
Concierge message comes in
Verify a concierge message is received and the content of this message matches purpose selected in the onboarding modal (see high level for purpose⇔concierge mapping)
[Web only] Verify newest message from concierge is opened in the central panel
[Mobile only] Verify user lands on the chats screen, but the newest message is not automatically opened
Video modal shows up
Verify after a small delay video modal is shown
Verify video modal can be dismissed at any time by clicking on the grayed out area or by clicking on the Let's go button
Verify video autostarts
Verify video shows no controls except for the volume slider
Verify video shows progress bar in the bottom
Verify video can be paused/resumed by clicking anywhere on the video
Verify video plays in a loop
Verify on page refresh the onboarding video disappears, even if user did not close it explicitly
Verify when going offline video keeps playing if it already buffered enough data

Account creation -> Onboarding modal completed -> [Offline mode] Onboarding video

Go to staging.new.expensify.com
Log in and navigate through Profile > About > Troubleshoot and press the 'Navigate' button next to Onboarding flow label
Fill in name and surname and hit Continue
Select any option in the What do you want to do today? Screen and hit Continue
Onboarding modal closes
Verify after a small delay video modal is shown
Verify instead of the video, a lottie animation is shown
Verify dismissing the onboarding video modal works like in online mode
Verify switching from offline to online hides the lottie animation and shows the video. The video starts loading immediately and autoplays. From this point test the video like in online mode.

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR
- [x] I added steps for local testing in the Tests section
- [x] I added steps for the expected offline behavior in the Offline steps section
- [x] I added steps for Staging and/or Production testing in the QA steps section
- [x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- [x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- [x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:
- [x] Android: Native
- [x] Android: mWeb Chrome
- [x] iOS: Native
- [x] iOS: mWeb Safari
- [x] MacOS: Chrome / Safari
- [x] MacOS: Desktop
[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)
- [x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
- [x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- [x] I verified that comments were added to code that is not self explanatory
- [x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- [x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  - [x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- [x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- [x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- [x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- [x] I verified the JSDocs style guidelines (in STYLE.md) were followed
[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:
- [x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
[x] If a new CSS style is added I verified that:
- [x] A similar style doesn't already exist
- [x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:
- [x] I verified that all the inputs inside a form are aligned with each other.
- [x] I added Design label so the design team can review the changes.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/88325488/e2387481-805e-4552-8599-ebaa3ca9e30f

Android: mWeb Chrome

https://github.com/Expensify/App/assets/88325488/a2d9c716-9b93-463c-aa58-a369b2babcc7

iOS: Native

https://github.com/Expensify/App/assets/88325488/1e14c222-cca8-4507-bf97-0894c9d43498

iOS: mWeb Safari

https://github.com/Expensify/App/assets/88325488/34b2625f-e941-4800-8f8d-8ff37d4fc203

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/88325488/47479b53-a32a-4c79-a819-95741cffdfc6

MacOS: Desktop

https://github.com/Expensify/App/assets/88325488/9ac435b1-96c2-447a-92ba-831909e43c53

Mar 05 '24 11:03 MaciejSWM