On 13-07-17 3:57 PM, Margaret Leibovic wrote:
It looks like you worked out a possible solution in that bug, but I
would love to hear an update if you do land a system to test chrome JS.
There are probably plenty of gaps in our test coverage that could help
fix. In particular, it would be nice to see some automated tests to
exercise add-on APIs that we don't use ourselves, since that's often a
source of regressions.
Hi margaret,
Bug 870908 [1] added a version of xpcshell's head.js and a
TestJavascript robocop base class for testing chrome javascript.
Here are some examples that test JS components that need to talk to Java
(so that xpcshell is not appropriate):
http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/tests/testOrderedBroadcast.js
http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/tests/testSharedPreferences.js
http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/tests/testDeviceSearchEngine.js
Myself and gbrown can answer any questions you might have.
Nick
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=870908
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev
