1068616 - Date&Time settings screen not skipped when data connection is available

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Gaia::First Time Experience, defect)

Description

[Florin Strugariu [:Bebe]]

Description:

User is prompted for Date&Time information even if a SIM with data connection is present

Repro Steps:

1. Open FTU app
2. Go through the steps and connect to cell data and wifi
3. Tap next after the WIFI connection

Actual:
3. The Date&Time view is visible

Expected: 
3. The Geolocation view should be visible as Date and time is  autodetected


Traceback (most recent call last):
  File "/home/florinstrugariu/.virtualenvs/gaia/local/lib/python2.7/site-packages/marionette_client-0.8.4-py2.7.egg/marionette/marionette_test.py", line 264, in run
    testMethod()
  File "/home/florinstrugariu/gaia/gaia/tests/python/gaia-ui-tests/gaiatest/tests/functional/ftu/test_ftu_skip_tour.py", line 73, in test_ftu_skip_tour
    self.ftu.tap_next_to_geolocation_section()
  File "/home/florinstrugariu/gaia/gaia/tests/python/gaia-ui-tests/gaiatest/apps/ftu/app.py", line 201, in tap_next_to_geolocation_section
    self.wait_for_element_displayed(*self._section_geolocation_locator)
  File "/home/florinstrugariu/gaia/gaia/tests/python/gaia-ui-tests/gaiatest/apps/base.py", line 44, in wait_for_element_displayed
    lambda m: m.find_element(by, locator).is_displayed())
  File "/home/florinstrugariu/.virtualenvs/gaia/local/lib/python2.7/site-packages/marionette_client-0.8.4-py2.7.egg/marionette/wait.py", line 143, in until
    cause=last_exc)


Environmental Variables:

Gaia-Rev        ba0b6816539d71bce2bb520d17297e1643fc477c
Gecko-Rev       https://hg.mozilla.org/integration/b2g-inbound/rev/b662a294b3cf
Build ID        20140917043758
Version         35.0a1
Device Name     flame
FW-Release      4.3
FW-Incremental  110
FW-Date         Fri Jun 27 15:57:58 CST 2014
Bootloader      L1TC00011230

Reproducible manually: YES

Repro frequency: 5/5

Regresion range:

Last good build:
Device firmware (date) 	31 Aug 2014 13:31:23
Device firmware (incremental) 	eng.cltbld.20140831.163113
Device firmware (release) 	4.3
Device identifier 	flame
Gaia date 	16 Sep 2014 19:58:24
Gaia revision 	76b9f7dfa83c
Gecko build 	20140916202257
Gecko revision 	8538c4294084
Gecko version 	35.0a1


First bad build:
Device firmware (date) 	31 Aug 2014 13:31:23
Device firmware (incremental) 	eng.cltbld.20140831.163113
Device firmware (release) 	4.3
Device identifier 	flame
Gaia date 	16 Sep 2014 20:17:21
Gaia revision 	7426a6282feb
Gecko build 	20140916204258
Gecko revision 	9a6be8571076
Gecko version 	35.0a1

Gaia diff:
https://github.com/mozilla-b2g/gaia/compare/76b9f7dfa83c...7426a6282feb

Geko diff:
http://hg.mozilla.org/integration/b2g-inbound/pushloghtml?fromchange=8538c4294084&tochange=9a6be8571076

Comment 1

[Zac C (:zac)]

Merged:
https://github.com/mozilla-b2g/gaia/commit/a912833545f5f024f9e2f09030072d3f8b29e309

Comment 2

[Florin Strugariu [:Bebe]]

This bug is still valid we just xfailed the test in that commit

Comment 3

[Zac C (:zac)]

Oops my mistake. 

This is blocking test coverage now.

Comment 4

[Jason Smith [:jsmith]]

Ted - Any ideas?

Comment 5

[Jason Smith [:jsmith]]

[Blocking Requested - why for this release]:

QA blocking regression from a 2.1+ bug fix.

Comment 6

[Michael Henretty [:mikehenrty][:mhenretty]]

Ted, this will most likely be a blocker. Assigning to you since you know this code best.

Comment 7

[Ted Clancy [:tedders1]]

It works for me. 

It's possible that the phone just hasn't found the mobile network by the time the user gets to the Date & Time screen. 

Florin, do you see the "signal strength bars" at the top of the phone? Do they show that the phone is connected to the wireless network when you do this test?

Comment 8

[Florin Strugariu [:Bebe]]

Attachment: 2014-09-18-14-51-19.png

I can still reproduce this issue on my device using:

Gaia-Rev        72262d054ffa5d0d2b5a0033f713149281511aea
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/4f2cac8d72da
Build ID        20140917160215
Version         35.0a1
Device Name     flame
FW-Release      4.3
FW-Incremental  110
FW-Date         Fri Jun 27 15:57:58 CST 2014
Bootloader      L1TC00011230


We check in the tests that the phone has cell connection and it can connect to cellular data.
Also We connect to a wifi network.

This test is failing constantly on our automation grid.

Comment 9

[Gregor Wagner [:gwagner]]

Ted, can you provide a logging patch so we can see whats going on?

Comment 10

[Gregor Wagner [:gwagner]]

Broken feature.

Comment 11

[Jason Smith [:jsmith]]

Can QAnalysts try to see if they can reproduce this?

Comment 12

[Adam Alldredge [:AdamA][Inactive]]

I was unable to reproduce this issue on the KK base or on the JB base.

Environmental Variables:
Device: Flame 2.2 Master
BuildID: 20140917212258
Gaia: d37950eb09e28aa18d0e01df9ff90574bd4337e0
Gecko: 426497473505
Version: 35.0a1 (2.2 Master)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Repro Rate: 0/5

Device: Flame 2.2 Master
BuildID: 20140917114258
Gaia: 72262d054ffa5d0d2b5a0033f713149281511aea
Gecko: d2c01d77b9d0
Version: 35.0a1 (2.2 Master)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Repro Rate: 0/5

Device: Flame 2.2 Master
BuildID: 20140917212258
Gaia: d37950eb09e28aa18d0e01df9ff90574bd4337e0
Gecko: 426497473505
Version: 35.0a1 (2.2 Master)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Repro Rate: 0/5

Comment 13

[Joshua Mitchell (Inactive)]

Can we get a build # for a specific location that you have reproduced this manually?

Comment 14

[Florin Strugariu [:Bebe]]

I retested this again.

The issue is not reproducible on a clean build (fresh flash). 
Tested this on:

Gaia-Rev        bc2da39ccd2b82b67773f10c8da8fc8eedc483ab
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/c8e325eee9e1
Build ID        20140918160202
Version         35.0a1
Device Name     flame
FW-Release      4.3
FW-Incremental  110
FW-Date         Fri Jun 27 15:57:58 CST 2014
Bootloader      L1TC00011230



The issue is 10/10 reproducible if we run any of our tests on the device testing this manually and with automation.


I still this issue is still a bug as it's breaking our automation test run

Comment 15

[Zac C (:zac)]

(In reply to Florin Strugariu [:Bebe] from comment #14)
> I retested this again.
> 
> The issue is not reproducible on a clean build (fresh flash). 
> Tested this on:
> 
> Gaia-Rev        bc2da39ccd2b82b67773f10c8da8fc8eedc483ab
> Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/c8e325eee9e1
> Build ID        20140918160202
> Version         35.0a1
> Device Name     flame
> FW-Release      4.3
> FW-Incremental  110
> FW-Date         Fri Jun 27 15:57:58 CST 2014
> Bootloader      L1TC00011230
> 
> 
> 
> The issue is 10/10 reproducible if we run any of our tests on the device
> testing this manually and with automation.
> 
> 
> I still this issue is still a bug as it's breaking our automation test run

You said in there it's not an issue but it is also an issue?

Please be clear about where/which builds it's failing - b2g-i or m-c ?

Why it is passing on that m-c build then?

Comment 16

[Florin Strugariu [:Bebe]]

After more investigation I found out that the test fail is because of our tests.

In the setup part of the test we set the timezone for test consistency. Because of this we see this FTU view.

Comment 17

[Florin Strugariu [:Bebe]]

Closing this as it's a test issue