1960964 - Create marionette test to verify data upload pref copying between profiles

Status: ASSIGNED

(Toolkit :: Startup and Profile System, enhancement, P3)

Comment 1

[Rebecca]

https://searchfox.org/mozilla-central/search?q=&path=browser**marionette&case=false&regexp=false

matrix: Firefox Testing

Comment 2

[Teddy Bersentes]

Attachment: Bug 1960964 - Implement marionette testing for multi-instance pref syncing. r=jhirsch

Comment 3

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Attachment: Bug 1960964 - Create multiple profiles and connect Marionette to two separate instances in the same test. r?#profiles-reviewers,whimboo

An initial patch - looking for feedback on the general approach.

Rather than override existing DesktopInstance behavior, create a new
DesktopSelectableProfileInstance subclass of DesktopInstance that
overrides _update_profile to simply assign the passed-in profile to
self._profile, avoiding the existing clone-or-create logic.

Unfortunately, because we need to use a non-standard port for a second
session, and because this port needs to be hard-coded in the profile
before it is launched, we have to modify the Marionette client
constructor to allow a profile to be passed in directly. Using the
obviously wrong "specialprofile" argument for now, and we'll see what
the Marionette experts suggest instead.

Many things still TODO, including:

• cleanup correctly:
  • remove the marionette profile from profiles.ini at end of test
  • remove the SQLite database file shared by the profile group
  • remove the additional profile from the user profiles directory
  • investigate mocking out directory service so the additional profiles
    and cross-profile SQLite database go in TmpD not UAppData
• actually test the cross-profile pref passing behavior
• add tests for marionette changes