On Fri, Nov 4, 2011 at 7:16 PM, Ryosuke Niwa <rn...@webkit.org> wrote:
> On Fri, Nov 4, 2011 at 7:07 PM, Ojan Vafai <o...@chromium.org> wrote: > >> On Fri, Nov 4, 2011 at 7:03 PM, Ryosuke Niwa <rn...@webkit.org> wrote: >> >>> I am, but I'm particularly concerned about W3C tests. It'll be nice if >>> we had exactly one way of running / writing ref tests. I think we can >>> easily automate the process of generating manifest files. >>> >>> The work flow will be as follows: >>> >>> 1. Write new ref tests using link element >>> 2. Run some tool (maybe we can teach run-webkit-tests to do it >>> automatically) >>> 3. Upload patch with auto-regenerated manifest file >>> >>> It's mainly step 2 that I have a problem with, although I also don't >> like that the test is not self-contained. >> > > Generating manifest file when we add a test is much more efficient than > generating it every time we run tests because we tend to do the latter much > more often than the former. > I think we're at an empass here. I don't see that further technical arguments will sway either of us. I do, however, expect that the vast majority of webkit developers would prefer to avoid a manifest file given the way the project has been structured up to now.
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
