On 06/05/2015 15:14, Andrew Halberstadt wrote:
Yeah, you shouldn't notice any difference when running from mach. The
only change is that the harness is handling defaults instead of the mach
command, and that they now both have the same command line. I think what
you are thinking of is when you run a single test. In that case
--keep-open is set for plain, but not browser. I'm not really sure why
that's the case, but the behaviour was preserved.
Great!
What does -f mean here and why would I want to change from
mochitest-browser to the longer mochitest -f browser ?
-f is --flavor. When running a single flavor there's not really any
benefit to using one vs the other. It just seems redundant to have N
commands when 1 is enough, but if there is widespread opposition to
removing mochitest-<flavor> it's not a huge deal to keep them.
Do I need to pass flavor? What would happen if I do:
./mach mochitest path/to/dir/with/only/mochitest-browser/things
-- would that "just work" ?
I mean, I thought that the original plan was for everybody to just use:
./mach test path/to/test
except it doesn't support half as many options as the actual test suites
(--start-at, --end-at, --jsdebugger, to name a few), so (for me
personally...) it's near enough useless in practice.
I'm all for simplifying the (mach) commands to run, as long as it
doesn't come with the cost of losing hard-won debugging options.
~ Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
