Also, looking at the config, I see that this only runs robocop unit tests. What about the other test suites we have, like mochitests? I understand wanting to avoid running all platform unit tests, but we do have mobile-specific tests besides robocop: https://dxr.mozilla.org/mozilla-central/source/mobile/android/tests/browser/chrome
I usually just run "-u all" to be safe, but maybe there's a better solution than that. Margaret On Mon, Apr 4, 2016 at 10:35 AM, Margaret Leibovic <mleibo...@mozilla.com> wrote: > Hey Mike, > > I re-ran `mach mercurial-setup`, assuming that would install this > extension as well, but I don't see it installed. Do I need to manually > install it? Are there plans to make this part of the official workflow? > > Thanks, > Margaret > > On Thu, Mar 31, 2016 at 10:14 AM, Michael Comella < > michael.l.come...@gmail.com> wrote: > >> Hey all. >> >> I wrote a wrapper around `hg push-to-try` that will run all of the >> Android try jobs using the latest configuration without try syntax [1]. >> After installing, run with: >> >> push-to-try-android >> >> If you want to avoid pushing but print the try syntax (e.g. to manually >> remove jobs or to copy-pasta in reviewboard): >> >> push-to-try-android --dry-run >> >> Finally, it pulls its configuration from github [2] so if it's ever >> out-of-date, pull requests are welcome! :) >> - Mike (:mcomella) >> >> [1]: https://github.com/mcomella/push-to-try-android >> [2]: >> https://github.com/mcomella/push-to-try-android/blob/master/config.json >> >> _______________________________________________ >> mobile-firefox-dev mailing list >> mobile-firefox-dev@mozilla.org >> https://mail.mozilla.org/listinfo/mobile-firefox-dev >> >> >
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
