1206012 - Firefox Sync initial test plan draft

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Sync, defect)

Comment 1

[Fernando Jiménez Moreno [:ferjm]]

Attachment: Test cases

Comment 2

[Fernando Jiménez Moreno [:ferjm]]

Attachment: Test cases

Comment 3

[Michiel de Jong [:michielbdejong]]

* What's the difference between:

>> Firefox Sync enabled screen should appear.
>> The displayed user should be the one used to login in Firefox Accounts.

in 1.4 and 2.3, versus:

>> [...] should show the Sync logged in user screen.
>> The state should remain the same after rebooting in both cases.

at the end of 4.4?

* [not really related to this bug] Are https://accounts.firefox.com/legal/terms and https://accounts.firefox.com/legal/privacy the right links? Do we need someone from legal to confirm that?

* Nit: an browse -> and browse (2x)

* [not really related to this bug] Reading 8.1 and 8.2, if a user executes 8.1 but forgets to execute 8.2, we get in a funny state where Sync is enabled for zero collections. I've opened bug 1208362 about this.

* [not really related to this bug] Not sure if I like the UX of this sequence:
15.4. Before the sync process is completed, tap on 'Disable Firefox Sync'.
>> The Firefox Sync disabled screen should be shown.
15.5. Tap on 'Getting Started'
What if I just disable sync because I'm roaming, or I want to save battery, then I would like to go to a state where sync is disabled "temporarily", but my sync settings (which collections to sync) are remembered. Going all the way back to the "Getting Started" screen seems a bit destructive.

* Re "15.3. Wait *at least* 120 seconds.", I would think we want to do the first sync immediately once the phone is done booting, or once Sync is enabled, so then the Sync interval has no influence on that?

Comment 4

[Fernando Jiménez Moreno [:ferjm]]

(In reply to Michiel de Jong [:michielbdejong] from comment #3)
> * What's the difference between:
> 
> >> Firefox Sync enabled screen should appear.
> >> The displayed user should be the one used to login in Firefox Accounts.
> 
> in 1.4 and 2.3, versus:
> 
> >> [...] should show the Sync logged in user screen.
> >> The state should remain the same after rebooting in both cases.
> 
> at the end of 4.4?
> 

Actually, I am changing case (4) to make it the same as case (3). On 2.5, even if the user can verify the account it won't be able to use the account with Sync until it uses the same account on Desktop or Android. So it's better to skip the unverified fxa screen for now and directly show the inactive sync account.

> * [not really related to this bug] Are
> https://accounts.firefox.com/legal/terms and
> https://accounts.firefox.com/legal/privacy the right links? Do we need
> someone from legal to confirm that?
> 

I took these links from Desktop Sync and Android Sync.

> * Nit: an browse -> and browse (2x)
> 
> * [not really related to this bug] Reading 8.1 and 8.2, if a user executes
> 8.1 but forgets to execute 8.2, we get in a funny state where Sync is
> enabled for zero collections. I've opened bug 1208362 about this.
> 
> * [not really related to this bug] Not sure if I like the UX of this
> sequence:
> 15.4. Before the sync process is completed, tap on 'Disable Firefox Sync'.
> >> The Firefox Sync disabled screen should be shown.
> 15.5. Tap on 'Getting Started'
> What if I just disable sync because I'm roaming, or I want to save battery,
> then I would like to go to a state where sync is disabled "temporarily", but
> my sync settings (which collections to sync) are remembered. Going all the
> way back to the "Getting Started" screen seems a bit destructive.
> 

Going back to the "Getting Started" screen doesn't reset any setting, so you will have the same collections enabled when you enable sync again.

> * Re "15.3. Wait *at least* 120 seconds.", I would think we want to do the
> first sync immediately once the phone is done booting, or once Sync is
> enabled, so then the Sync interval has no influence on that?

requestSync is supposed to take care of this. Expired timers are supposed to fire when the device boots.

Comment 5

[Fernando Jiménez Moreno [:ferjm]]

Attachment: Test cases

Comment 6

[Fernando Jiménez Moreno [:ferjm]]

I am resolving fixed this based on Michiel's r+. We can make improvements to these test cases once we have support from the QA team.