1254154 - TEST-UNEXPECTED-FAIL | apps/system/test/marionette/lockscreen_unlock_to_homescreen_test.js | LockScreen > passcode is disabled so it will slide to unlock to homescreen

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::System, defect)

Description

[Alberto Pastor [:albertopq]]

https://public-artifacts.taskcluster.net/KQVI3LsTTb-GPv6GMPZ7ew/3/public/logs/live_backing.log

Comment 1

[GitHub Autolander Bot]

Attachment: [gaia] albertopq:1254154-lockscreen-intermittent > mozilla-b2g:master

Comment 2

[Alberto Pastor [:albertopq]]

Again, it seems that 'element.displayed()' is not working properly (Bug 1251574 had the same issue).

This patch is a workaround, but I guess we should fix the original issue? Aus?

Comment 3

[Aus Lacroix [:aus]]

I think the issue is that the element you're waiting for visibility on is still not accessible when it's visible. This will throw an error and cause this type of issue. I'm honestly not sure what's involved in making sure the item is screen reader accessible in this case by yzen would know.

You can also disable a11y checks like this -- https://github.com/yzen/gaia/blob/5e8c1eacb38cd83a5de87888d6bb6a72ee392a84/apps/calendar/test/marionette/alarm_test.js#L21

This might remedy your situation.

Comment 4

[Alberto Pastor [:albertopq]]

Mhm, I'm not sure. Is not raising an error, but timing out waiting for an element to be hidden (when the element is not visible anymore). Apart from that, accessibility exceptions are already disabled on that test [1].

I think I'll land the workaround for now. Thanks for the info!

[1] https://github.com/mozilla-b2g/gaia/blob/master/apps/system/test/marionette/lockscreen_unlock_to_homescreen_test.js#L13

Comment 5

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

Comment on attachment 8727430 [details] [review]
[gaia] albertopq:1254154-lockscreen-intermittent > mozilla-b2g:master

Thanks!

Comment 6

[Alberto Pastor [:albertopq]]

master: https://github.com/mozilla-b2g/gaia/commit/16f5f723421247daf5e576c210c51f86b31ed77b