mochitest-chrome tests now running on B2G emulators

A mochitest-chrome job is now running on B2G emulators, and appears in
Treeherder as M(c).  This job skips most existing chrome tests, since most
of the existing tests are not compatible with B2G.  But it provides a
better alternative when writing mochitests that need chrome privileges than
using SpecialPowers in mochitest-plain.

If you want your new chrome mochitest to get run on B2G, just make sure
it's written as an XHTML file and not a XUL one; see
https://dxr.mozilla.org/mozilla-central/source/testing/mochitest/static/chrome.template.txt
..

If you don't want your new chrome mochitest to run on B2G, just add
"skip-if = buildapp == 'b2g'" to the relevant chrome.ini manifest.

To run the tests locally, just add a --chrome argument to your
runtestsb2g.py command-line, as documented here:
https://developer.mozilla.org/en-US/Firefox_OS/Platform/Automated_testing/Mochitests#Running_the_tests_2

Regards,

Jonathan
0
Jonathan
3/23/2015 11:38:06 PM
mozilla.dev.platform 6646 articles. 0 followers. Post Follow

0 Replies
546 Views

Similar Articles

[PageSpeed] 12

Reply:

Similar Artilces:

Running XPCShell tests on B2G emulator
--20cf303ea6a6a736c4050482e46a Content-Type: text/plain; charset=UTF-8 Hi, what's the best way to run XPCShell tests on the B2G emulator? In the past I managed to workaround the need of running these tests locally. But now I really have no other choice and I am having a really hard time trying to run them locally. I am following the guide at [1], but I found several issues, like [2] not existing anymore for instance. After struggling to install all the dependencies I think I managed to trigger the XPCShell tests machinery with the following command: runtestsb2g.py --adb...

how to run the b2g emulator cppunit tests?
Hi friends! I'm currently working on a networking patch for b2g (bug 1008091), but when I send it on a try-run adventure I get cppunit test failures on the b2g emulator. So, I built my own emulator locally and I want to run the cppunit test to see for myself what happens and track down the problem with my patch. How do I run the cppunit tests like the try run do? My searches seem to fail me. -- / daniel.haxx.se On Tuesday, 28 October 2014 06:59:15 UTC-4, Daniel Stenberg wrote: > Hi friends! >=20 > I'm currently working on a networking patch for ...

B2G desktop mochitests now running
Just an fyi, b2g desktop mochitests are now running on all mozilla-central based branches (this does not include mozilla-b2g26, though if this is desired, I can look into it). They are running the same set of mochitests as the b2g emulators, minus a few that had b2g desktop specific issues (see bug 931116 for a list of which ones). Please file test issues as blocking bugs to bug 931116. The biggest outstanding issue is the inability to run a single test via mach (see bug 927889 for more details or if you'd like to help investigate). Thanks, Andrew ...

B2G mochitests now use mochitest.ini manifests instead of b2g.json
For awhile now we've been using these hacky JSON based manifests to enable and disable mochitests on B2G. Now, thanks to the work of an awesome contributor (vaibhav1994), all the B2G mochitests are using the mochitest.ini format. This allows us to annotate tests with metadata, like whether the test should be skipped or not. What does this mean for you? If you are enabling/disabling, or adding a new mochitest, you now need to edit the 'mochitest.ini' file which lives in the same directory as your test file. For example, if I want to disable dom/media/tests/mochit...

web-platform-tests now running in automation
The web-platform-tests testsuite has just landed on Mozilla-Central. It is an import of a testsuite collated by the W3C [1], which we intend to keep up-to-date with upstream. The tests are located in /testing/web-platform/tests/ and are now running in automation. Initially the testsuite, excluding the reftests, is running on Linux 64 opt builds only. If it doesn't cause problems there it will be rolled out to other configurations, once we are confident they will be equally stable. The jobs indicated on tbpl and treeherder by the symbols W1-W4. The reftests will be Wr once they...

datetime.now() and datetime.now().addmonths()..insert code run before.. but it doesnt run now... i have no done anything.. why dont it run itself ?
hi datetime.now() and datetime.now().addmonths().. it run before.. but it doesnt run now... i have no done anything.. why doesnt it run now ? my datatype is datetime.. what can problem be ? sds.InsertParameters.Add("ilanbaslangictarihi", DateTime.Now()) hello friends when i change 14.06.2008 to 10.06.2008 from my computer, inserting run for datetime.now() but when i change 10.06.2008 to 14.06.2008 from my computer.. inserting doesnt run for datetime.now() Also when i enter {0:dd/MM/YYYY hh:mm:ss} to formatstring of edit column of gridview, gridview display 33.06.2008 1...

Can we improve emulator testing? (Was: Running on-device tests in CI)
On Jun 3, 2014 2:25 PM, "Jonathan Griffin" <jgriffin@mozilla.com> wrote: > There have been a couple of threads related to test automation in B2G, asking why we haven't caught some especially egregious regressions; the kind that basically "break the phone". It's great to hear that we are making progress on on-device testing. Testing on device is always going to be needed and desired as ultimately, having FirefoxOS working on device is what matters to users. However I'm curious why emulator testing didn't catch these recent regressions? Did...

How do we test (or, going to test) gecko/b2g/chrome/content/*.js ?
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.j...

Can we improve emulator testing? (Was: Running on-device tests in CI)
On Jun 3, 2014 2:25 PM, "Jonathan Griffin" <jgriffin@mozilla.com> wrote: > There have been a couple of threads related to test automation in B2G, asking why we haven't caught some especially egregious regressions; the kind that basically "break the phone". It's great to hear that we are making progress on on-device testing. Testing on device is always going to be needed and desired as ultimately, having FirefoxOS working on device is what matters to users. However I'm curious why emulator testing didn't catch these recent regressions? Did...

mochitest-browser-chrome now split out from mochitest-other
At the end of last week, mochitest-browser-chrome was split out from mochitest-other (bug 791389), roughly halving the time taken for mochitest-other to complete. Trychooser [1] has been updated, but if you either type from memory or use saved MQs, please use 'mochitest-bc' if mochitest-browser-chrome is needed, since 'mochitest-o' will no longer cause it to be run. For those interested in the benefits of splitting it out, see: https://bugzilla.mozilla.org/show_bug.cgi?id=791389#c1 With b-c removed, the remaining mochitest-other suites are: * mochitest-chrome * moch...

running mochitests in emulator
Hi, i've been trying to run a mochitest in the emulator (ARM) without much luck. i got the emulator running on Ubuntu 12.04 finally (i couldn't get it to start on 12.10) i built against a local Gecko with my patch including my test applied and the emulator also seems to start up and 'work' normally building against that. i installed setuputils and ran python setup.py develop in my local Gecko's testing/marionette/client directory. when i try to run my mochitest from ~/src/mozilla-central/objdir-gonk-dbg/_tests/testing/mochitest using: python runtests...

It is now possible to apply arbitrary tags to tests/manifests and run all tests with a given tag
As of bug 987360, you can now run all tests with a given tag for mochitest (and variants), xpcshell and marionette based harnesses. Tags can be applied to either individual tests, or the DEFAULT section in manifests. Tests can have multiple tags, in which case they should be comma delimited. To run all tests with a given tag, pass in --tag <tag name> to the mach command. For example, let's say we want to group all mochitest-plain tests related to canvas together. First we'd add a 'canvas' tag to the DEFAULT section in https://dxr.mozilla.org/mozilla-cen...

test test test test test test
test test test test test test test test test test test ...

mailman config changed; text/html should now show up in dev-gaia and dev-b2g and links should not be corrupted
This is a multi-part message in MIME format. --------------040907020305070007060305 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Assuming all has gone well, the mailman list-server software we use for dev-b2g and dev-gaia should no longer force multipart/alternative mail messages to use the first sub-part (which is likely to be text/plain). What this means is that if you use the gmail web UI to talk on the list and your hyperlinks have ended up messed up, that should stop happening. (This, by definition, is/was a bug in gmail'...

Web resources about - mochitest-chrome tests now running on B2G emulators - mozilla.dev.platform

Resources last updated: 1/19/2016 9:13:18 PM