I think before trying to resurrect browser-chrome tests for B2G, it's
important to understand what these tests need to do; there may be an
alternate that already works.
Back when B2G began, the only test harness we initially had was
mochitest-browser-chrome. All it did was to load and execute JS files
in the parent process, along with the ability to verify test
assertions. It was a very minimal system. It had no built-in capacity
to talk to content running in remote processes (at the time, B2G was
single-process only).
If all you need to do is execute some JS in the parent process, you can
already do that with WebAPI JS tests, although these are currently only
running on the emulator. If you need something else, then
browser-chrome probably isn't the right framework anyway.
Ping me if you'd like so we can figure this out.
Jonathan Griffin
On 11/6/13 5:25 AM, Alexandre poirot wrote:
Tim, Do you know that in the early days of gaia, gaia was using
mochitest-browser-chrome tests?
There is still some relic of the past over here:
https://github.com/mozilla-b2g/gaia/tree/master/tests
And even a make target to run them, that requires a local b2g desktop build:
https://github.com/mozilla-b2g/gaia/blob/master/Makefile#L710-L715
But it is being broken now.
Jonathan, Would it be hard to run mochitest-browser-chrome tests for b2g
desktop on TBPL, exactly like firefox, but just with a different set of
test files? We could take care of ensuring that "./mach mochitest-browser"
and "make -C objdir mochitest-browser-chrome" works again on b2g desktop.
2013/11/5 J. Ryan Stinnett <[email protected]>
This would also be valuable for the App Manager team. We'd like to be able
to test how the DebuggerServer is started on B2G, as we currently see a lot
of breakages there since there is no coverage of this code path.
Is anything I can do to help make a case for including a test runner like
this for B2G? Do we have any estimates of the level of effort involved to
make it work?
Browser chrome tests definitely seem like the most natural test suite for
this type of testing.
- Ryan
On Tuesday, October 29, 2013 5:42:54 AM UTC-5, Tim Chien wrote:
Thanks for the information.
I highly recommend to prioritize this work. These are the two scripts
that sits in the critical launch path of the phone. If it breaks the
phone won't boot, and it did due to many suspectable race conditions
we found previously...
On Tue, Oct 29, 2013 at 5:53 AM, Jonathan Griffin <[email protected]>
wrote:
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
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
