1013830 - [LockScreen][UI Tests][Accessibility] Enable UI tests after the LockScreen as an app landed

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia, defect)

Description

[Greg Weng [:snowmantw][:gweng][:λ]]

I've found that I have no clue how to make the a11y related LockScreen tests works, because I lack of the knowledges to fix them properly. So I want to disable them and CC experts to help me to fix them.

There are two tests should be fixed:

test_a11y_unlock_to_camera.py
test_a11y_unlock_to_homescreen.py

Comment 1

[Greg Weng [:snowmantw][:gweng][:λ]]

The as-an-app bug, with the WIP patch is Bug 898348.

Comment 2

[Marco Zehe (:MarcoZ)]

Gregg, if this helps: These tests test the buttons that are displayed when the screen reader is running. This is to make going to the camera, and unlocking the phone, easier for blind screen reader users, since they can't easily do the "slide to unlock", or whatever the actual non-screen-reader gesture on Firefox OS is. I am blind myself, so don't even know if this is still the curtain that you have to lift before you can unlock the phone, or if this changed in the meantime.

So what a blind user has to do is tap, or swipe to, then double-tap the button that says "Camera" or "Unlock".

The tests test whether these buttons become available, and work, as soon as the screen reader is detected running.

Comment 3

[Greg Weng [:snowmantw][:gweng][:λ]]

Thanks and it's helpful. However I still have to know how to map the current test under the new architecture, because currently the test seems directly fetch the lockscreen window and it's content, and this seems a little hacking. It would also be failed after the window become a real window, and the content would be inaccessible, which is the reason the current tests would be failed after the bug get landed.

Comment 4

[Marco Zehe (:MarcoZ)]

Sounds to me like the test logic needs to be moved into the tests for the Lock Screen app itself:
1. Turn on screen reader.
2. Test for the changed UI.
3. Turn screen reader back off.
Of course things get interesting the moment the camera and unlock buttons are activated and focus transitions to the other according app. :-)

I'l leave it to Eitan to actually look at this, though, since he can see what's going on when the screen reader is not running, while I cannot.

Comment 5

[Greg Weng [:snowmantw][:gweng][:λ]]

Since we need to change the plan to make LockScreen as-an-app, I would leave bug WONT fix, and find another way to complete the test cases in the new app.