On 11/05/2013 07:35 AM, James Graham wrote:
On 05/11/13 15:20, Till Schneidereit wrote:
Do we have any way to identify tests that break particularly often for
specific areas? If so, we could create a mach command that runs just
these
tests and finishes quickly. Something like `mach canary-tests`.
Isn't the end game for this kind of approach where you have a
(frequently, automatically updated) map of code to tests, so the
system knows that given a commit touches the code in file x, it seens
to run the set of tests {T_x}. One can imagine using such a system on
try to automatically run only the tests most likely to pick up
regressions.
IMHO yes. As is not uncommon knowledge, google has such a system. As is
also not uncommon knowledge, it is easier to come up with such a system
with the benefit of foresight than trying to backport existing
codebase+build system+infra to such a system.
It is a lot of work to create the infrastructure for this kind of
setup, however ...
Indeed
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
