We currently do not support browser_chrome_tests in B2G, and there are
no current plans to add support for it - all the existing browser_chrome
tests are Firefox-specific.
If there is a need for some hybrid gecko/gaia tests (and I believe there
likely is), we should carefully define what the capabilities of such
tests should be, so we can architect an appropriate solution.
Right now, I agree that gaia-ui-tests, or gaia-integration-tests (their
JS equivalents) are the best places to write such tests, even though
those frameworks may be slightly awkward for this kind of verification.
Jonathan
On 10/28/2013 7:58 AM, Tim Chien wrote:
Vivien,
Thanks, that's very helpful. IMHO we should push this work to the FxOS roadmap.
On Mon, Oct 28, 2013 at 6:57 PM, Vivien Nicolas <[email protected]> wrote:
You likely want:
https://developer.mozilla.org/en-US/docs/Mochitest
https://developer.mozilla.org/en-US/docs/Browser_chrome_tests
Cheers,
Vivien.
On 27/10/2013 08:57, Tim Chien wrote:
Hi,
While working on DNT feature, I realized that our Gaia integration tests
(Python and JS) can only assert the values of mozSettings database after
the test programically select the setting ratio button in the Setting app.
It is actually at [1] where we copy the value from mozSettings to Gecko
pref().
While the code there are relatively small, I wonder if we could write any
tests for them? Any pointer of documentation to write tests for this
particular part of Gecko is greatly appreciated. Thanks.
[1]
http://dxr.mozilla.org/mozilla-central/source/b2g/chrome/content/settings.js#l434
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
