On Fri, Sep 9, 2011 at 10:17 AM, Geoffrey Garen <gga...@apple.com> wrote: > I also think it’s good to have a WebKit-specific or specific-enough word in > script names when possible so you can have the scripts in your path even > when not working on WebKit. That’s why run-webkit-tests has the word WebKit > in it, and run-safari does not. > > I'd suggest one script -- run-webkit-tests -- with flags for including or > excluding specific testing (layout tests, unit tests, bindings tests, etc.). > That way, there's only one name to remember, you get a sensible default, and > you can always use --help to figure special subtest settings as necessary. > (I think a little bike shedding is OK here, since this is a tool we all use > every day.)
Note that the mechanisms for running each sub-suite may vary significantly, so practically the top-level script may just end up shelling out to subscripts anyway. That said, I agree that the top-level script should have the characteristics you describe. -- Dirk _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
