On 13/03/15 04:02 PM, Gregory Szorc wrote:
Another pain point: running all relevant tests.
Many features have relevant tests across many test suites, sometimes spread
across different directories. When people are hacking on a feature, they
should have a way to run all relevant tests for that feature. All too often
I've submitted something to Try (or worse landed without Try) only to find
out I wasn't locally running all tests relevant for the thing that changed.
I did some work in bug 987360 around test "tagging." e.g. "mach test fhr"
would run all tests tagged as relevant to Firefox Health Report.
How does this tagging work? Something that would be quite easy to do
would be to add a "label" attribute to the test manifest. This could be
a comma separated list of arbitrary strings (and could be applied to
either individual tests or entire manifests). E.g
[test_foo.js]
label=fhr,telemetry
./mach mochitest --label=fhr (or whatever)
IMO there's no need for the build to process this information, and
keeping it in the manifests has better visibility than moz.build.
-Andrew
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
