Skip to content

Conversation

@aitorvs
Copy link
Collaborator

@aitorvs aitorvs commented Jan 21, 2021

Task/Issue URL: https://app.asana.com/0/414730916066338/1199628713920165/f
Tech Design URL:
CC: https://app.asana.com/0/1142021229838617/1199633113249889/f

Description:
After the successfull experiment, see https://app.asana.com/0/0/1199361498013999/f, this PR:

  • Removes the zu and zt variants
  • Modifies the DefaultRoleBrowserDialogExperiment#shouldShowExperiment to remove the variant check
  • Modifies the OnboardingPageManagerWithTrackerBlocking to remove the variant check and to ensure it shows when the "new Chrome default browser dialog" does not
  • Fixed the tests

Steps to test this PR:

==Test case 1==

Device API >=29

  • Fresh install the app and launch it
  • In Welcome page press "let's do it"
  • Select ddg as default browser in the dialog
  • Verify app proceeds to main browser page
  • Verify pixel m_db_s with fo param set as true
  • Verify browser is set as default

==Test case 2==

  • Device API >=29
  • Fresh install the app and launch it
  • In Welcome page press "let's do it"
  • Press "Cancel" in the dialog
  • Verify app proceeds to main browser page
  • Verify pixel m_db_ns with fo param set as true
  • Verify browser is NOT set as default

==Test case 3==

  • Device API <29
  • Fresh install the app and launch it
  • In Welcome page press "let's do it"
  • Verify (legacy) onboarding proceeds unmodified

==Test case 4==

  • Device with any API
  • Upgrade the app and launch it (onboarding should have been done already)
  • Verify onboarding is skipped and user taken to main browser page

Internal references:

Software Engineering Expectations
Technical Design Template

@aitorvs aitorvs requested a review from marcosholgado January 21, 2021 08:56
@aitorvs aitorvs force-pushed the feature/aitor/new_default_browser_dialog_all_users branch from aaf432a to d74b9f4 Compare January 21, 2021 17:03
@marcosholgado marcosholgado self-assigned this Jan 25, 2021
Copy link
Contributor

@marcosholgado marcosholgado left a comment

Choose a reason for hiding this comment

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

Nice job. I left a few comments to rename tests and some methods and classes since we don't have an experiment or variants anymore. Other things to rename that are not in the PR are:

  1. WelcomePageViewModelTest has Xp in the test names which will make no sense when renaming shouldShowExperiment .
  2. DefaultRoleBrowserDialogExperiment has a method called experimentShown that we should also rename to something like dialogShown or similar.
  3. VariantManager has the unused method isAtLeastApiVersion

@aitorvs aitorvs force-pushed the feature/aitor/new_default_browser_dialog_all_users branch 2 times, most recently from 46a263b to 712c88b Compare January 25, 2021 10:46
@aitorvs
Copy link
Collaborator Author

aitorvs commented Jan 25, 2021

@marcosholgado thanks! I think I addressed all comments in the latest commit

@aitorvs aitorvs requested a review from marcosholgado January 25, 2021 10:47
* Renamed DefaultRoleBrowserDialogExperiment -> DefaultRoleBrowserDialog

* Renamed shouldShowExperiment -> shouldShowDialog

* Renamed experimentShown -> dialogShown

* Removed isAtLeastApiVersion

* Removed references to browser dialog variant in tests
@aitorvs aitorvs force-pushed the feature/aitor/new_default_browser_dialog_all_users branch from 712c88b to 56f3cba Compare January 25, 2021 10:52
Copy link
Contributor

@marcosholgado marcosholgado left a comment

Choose a reason for hiding this comment

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

LGTM! :shipit:

@prakharb5
Copy link

Does this PR lead to a new OOBE?

@aitorvs aitorvs merged commit e02df16 into develop Jan 25, 2021
@aitorvs aitorvs deleted the feature/aitor/new_default_browser_dialog_all_users branch January 25, 2021 17:40
@marcosholgado
Copy link
Contributor

Does this PR lead to a new OOBE?

@Cyberdroid1, If by OOBE you mean out of the box experience then the answer is yes.

@prakharb5
Copy link

Yes, I mean the out of box experience.

I would be looking forward to it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants