These tests don't actually take pictures, they just check the frames open. So let's see if we can enable the tests.
I ran the lockscreen camera tests several times on Travis, they passed: https://pastebin.mozilla.org/4173388, https://pastebin.mozilla.org/4173419 I will enable them on Travis and TBPL also. Let's see how they behave.
Created attachment 8369455 [details] [review] Github PR: https://github.com/mozilla-b2g/gaia/pull/15915
Attachment #8369455 - Flags: review- → review?(zcampbell)
Comment on attachment 8369455 [details] [review] Github PR: https://github.com/mozilla-b2g/gaia/pull/15915 r+ but I'll wait for a green Travis before I merge.
Attachment #8369455 - Flags: review?(zcampbell) → review+
Both of the tests failed on Travis.
As this tests failed on travis, I think we can close this bug.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(In reply to Viorela Ioia [:viorela] from comment #5) > As this tests failed on travis, I think we can close this bug. This doesn't make any sense to me. If the tests failed, why is this resolved/fixed?
Sorry, this should be marked as wontfix, since the test failed on Travis.
Resolution: FIXED → WONTFIX
But in comment 1 you mentioned that they passed for you, so shouldn't we expect them to pass?
The tests passed when I ran them locally, using the Travis script.
Exactly, so why are they failing on Travis? Shouldn't we look into that? :)
I just thought that locally Gecko could pick up on a camera in our laptops whereas on Travis it's a VM.
Camera can work in a VM too, it's probably more likely to be related to a lack of camera on the host. This bug just seemed to lack any proper resolution. I wouldn't really expect any tests using the camera app to pass on a target with no camera attached.
You need to log in before you can comment on or make changes to this bug.