A note about browser-chrome mochitests
felipc at gmail.com
Thu Sep 19 17:03:27 UTC 2013
As a tip, Hgweb does not follow file renames in the revision log, so all
you'll see by default is the cset of this file move, e.g.
However, you can see on that page that underneath the timestamp there's a
"base" link, and that will take you to the previous history of that file
before the rename.
Annotate works as expected, and also you can see the full log locally by
using `hg log --follow`
On Thu, Sep 19, 2013 at 3:12 AM, Jared Wein <jwein at mozilla.com> wrote:
> I just pushed to the fx-team repo a patch that moves the browser-chrome
> mochitests from /browser/base/content/tests/* to
> Moving the tests in browser/base/content/tests to
> browser/base/content/tests/general will shorten the amount of time needed
> to just run the "general" tests. Currently when running `mach
> mochitest-browser browser/base/content/test` the social and newtab tests
> run as well, which adds a considerable amount of time to the local test run.
> The newtab and social test directories will remain as direct children of
> With this bug fixed, the directory structure should look like:
> If there is any potential to move groups of tests that focus on specific
> functionality then those can move to their own specific folder in future
>  https://hg.mozilla.org/integration/fx-team/rev/d558e1102e02
>  https://bugzilla.mozilla.org/show_bug.cgi?id=917887
> firefox-dev mailing list
> firefox-dev at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the firefox-dev