Closed
Bug 924835
Opened 11 years ago
Closed 10 years ago
Create a test for receiving a call with a locked screen
Categories
(Firefox OS Graveyard :: Gaia::UI Tests, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: zcampbell, Assigned: viorela, Mentored)
References
Details
(Whiteboard: [lang=py])
Attachments
(1 file, 1 obsolete file)
1. Start the device 2. Lock the screen 3. Trigger a call with Plivo account 4. Assert that the incoming call screen shows up 5. Reject the incoming call 6. Check device is still locked.
Updated•10 years ago
|
QA Contact: bob.silverberg
Updated•10 years ago
|
Assignee: nobody → bob.silverberg
QA Contact: bob.silverberg
Comment 1•10 years ago
|
||
Bob Looks like this is unblocked Do you want to work on it or we can open it for other team members?
Priority: -- → P2
Comment 2•10 years ago
|
||
are you still working on this or we can give this to the community ?
Flags: needinfo?(bob.silverberg)
Whiteboard: [mentor=zac][mentor=bebe][lang=py]
Comment 3•10 years ago
|
||
It is free for the taking! Whoever works on it can use [1] as an example. [1] https://github.com/mozilla-b2g/gaia/blob/master/tests/python/gaia-ui-tests/gaiatest/tests/functional/dialer/test_dialer_receive_call.py
Assignee: bob.silverberg → nobody
Flags: needinfo?(bob.silverberg)
Updated•10 years ago
|
Mentor: zcampbell florin.strugariu
Mentor: florin.strugariu, zcampbell
Whiteboard: [mentor=zac][mentor=bebe][lang=py] → [lang=py]
Updated•10 years ago
|
Mentor: florin.strugariu, zcampbell
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → viorela.ioia
Assignee | ||
Comment 4•10 years ago
|
||
Attachment #8451469 -
Flags: review?(zcampbell)
Attachment #8451469 -
Flags: review?(andrei.hutusoru)
Comment 5•10 years ago
|
||
Comment on attachment 8451469 [details] [review] Github PR: https://github.com/mozilla-b2g/gaia/pull/21432 the tearDown will fail if the test fails before line 35 also if we make this live call let's check that: * we got the correct screen * We have the option to answer the call * we receive the call from the correct number * we see the notification with the missed call * we see the notification on the home screen Zac are these checks OK?
Attachment #8451469 -
Flags: review-
Flags: needinfo?(zcampbell)
Reporter | ||
Comment 6•10 years ago
|
||
I don't think we need any of those additional checks. Often just following the UI is sufficient. This is much more of a smoketest than highly detailed check.
Flags: needinfo?(zcampbell)
Reporter | ||
Comment 7•10 years ago
|
||
Comment on attachment 8451469 [details] [review] Github PR: https://github.com/mozilla-b2g/gaia/pull/21432 r+ thanks!
Attachment #8451469 -
Flags: review?(zcampbell) → review+
Comment 8•10 years ago
|
||
Comment on attachment 8451469 [details] [review] Github PR: https://github.com/mozilla-b2g/gaia/pull/21432 Runs great, code looks good.
Attachment #8451469 -
Flags: review?(andrei.hutusoru) → review+
Comment 9•10 years ago
|
||
Comment on attachment 8451469 [details] [review] Github PR: https://github.com/mozilla-b2g/gaia/pull/21432 LGTM
Attachment #8451469 -
Flags: review- → review+
Comment 10•10 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/996289a65c4178410009ec2f4b7bf890d8902b02
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 11•10 years ago
|
||
This was reverted in https://github.com/mozilla-b2g/gaia/commit/41ec15c3d96637be972a0cc16f3a1dfee0e75559 Viorela can you fix the manifest file please
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 12•10 years ago
|
||
Attachment #8451469 -
Attachment is obsolete: true
Attachment #8453734 -
Flags: review?(andrei.hutusoru)
Comment 13•10 years ago
|
||
Comment on attachment 8453734 [details] fixed manifest: https://github.com/mozilla-b2g/gaia/pull/21584/files MERGED: https://github.com/mozilla-b2g/gaia/commit/0767581bb860c72aef0b635dc32a60361413b4b7
Attachment #8453734 -
Flags: review?(andrei.hutusoru) → review+
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•