Closed
Bug 1109601
Opened 10 years ago
Closed 8 years ago
Add a test to check contact's photo when having an active call and receiving a new incoming call
Categories
(Firefox OS Graveyard :: Gaia::UI Tests, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jlorenzo, Assigned: jlorenzo)
References
Details
Attachments
(1 file)
From bug 1009596
STRs:
1- Launch Dialer app
2- Establish a call with contact A
3- Having an active call with contact A, receive an incoming call from contact B
EXPECTED RESULT:
The photo corresponding to contact A (The one with the active call) should be shown while receiving the new incoming call from contact B
Assignee | ||
Updated•10 years ago
|
QA Whiteboard: [fxosqa-auto-s6][fxosqa-auto-points=3]
Assignee | ||
Comment 1•10 years ago
|
||
I have a first shot here but the final assertion doesn't work. The blob uuid has changed. The image is still the same though. Do we expect a modification of the uuid?
Flags: needinfo?(thills)
Flags: needinfo?(drs.bugzilla)
Comment 2•10 years ago
|
||
We talked about this over IRC. Suffice it to say, we're setting the background image every time the calls change -- even if the image itself is the same. This causes the UUID to change. Our naive solution is to do a bit-by-bit comparison of the Blobs, but something tells me that there's a better way to do this.
Flags: needinfo?(thills)
Flags: needinfo?(drs.bugzilla)
Assignee | ||
Comment 3•10 years ago
|
||
I think we should implement this image comparison in the CallScreen itself. To my knowledge, the harness is not capable of doing that kind of operation. Furthermore, this would help us to avoid some flickering with an image which is not so small (like IMG_0001.jpg used in this test).
I opened bug 1112083 in that regard.
Assignee | ||
Updated•10 years ago
|
QA Whiteboard: [fxosqa-auto-s6][fxosqa-auto-points=3] → [fxosqa-auto-dropped-s6][fxosqa-auto-points=3]
Assignee | ||
Comment 4•8 years ago
|
||
Gaia UI tests are not run or maintained anymore.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•