916035 - Follow up bug for writing test on bug 913377

Status: RESOLVED INVALID

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

Description

[Joe Cheng [:jcheng] (please needinfo)]

Follow up bug for writing test on bug 913377

Comment 1

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

I've encountered a issue that the B2G launched by Marionette let neither my test nor the real mouse trigger events on the lockscreen, but directly clicking on icons or other components is okay. I've launched the same B2G in the gaia repo manually and it worked fine.

Comment 2

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

Evan and I encountered the same issue even on B2G itself without Marionette, and even with the previous version's lockscreen! So it should be a B2G problem and only happens on some versions. This may need a detailed check to find out what's going wrong. Meanwhile, I'll start to write unit tests instead.

Comment 3

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

I've tested that the click event will be fired on the B2G used by current Marionette, while the touch events NOT. At least this happens when the current app is system and the lockscreen component is just launched.

Comment 4

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

I've reported the B2G/Marionette issue related to this one: the touch events can't be fired if it use the 'profile-test' to initialize the B2G, while click events works fine. Moreover, if the B2G is launched manually with the 'profile-debug' generated by the Makefile, it would work fine.

Comment 5

[Ivan Tsay (:ITsay)]

Test case is not the blocker

Comment 6

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

Since Bug 891882 had been solved, I may start to write some integration tests for LockScreen.

Comment 7

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

LockScreen related components now already have several integration tests.