<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 4, 2013 at 11:19 AM, Darin Adler <span dir="ltr"><<a href="mailto:darin@apple.com" target="_blank">darin@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div class="im"><br><div><div>On Dec 4, 2013, at 6:48 AM, youenn fablet <<a href="mailto:youennf@gmail.com" target="_blank">youennf@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr">I am planning to add some XHR tests from <a href="https://github.com/w3c/web-platform-tests" style="font-family:arial,sans-serif;font-size:13px" target="_blank">https://github.com/w3c/web-platform-tests</a>. <div>
My initial plan was <font face="arial, sans-serif">to add them in a subdirectory of LayoutTests/http/tests/w3c.</font></div><div><span style="font-family:arial,sans-serif">If adding them into </span><font face="arial, sans-serif">LayoutTests/imported/w3c</font><span style="font-family:arial,sans-serif">, that would probably require updating </span><span style="font-family:arial,sans-serif">the test scripts to start/stop the HTTP test server for that particular sub-folder.</span><br>
</div><div><span style="font-family:arial,sans-serif"><br></span></div><div><font face="arial, sans-serif">Any preference?</font></div></div></blockquote><br></div></div><div>I’d prefer LayoutTests/imported/w3c. Although I’m not so happy about the different terminology we are using for “imported” vs. “ThirdParty”, which seems like the same concept at the top level of the directory structure.</div>
<div><br></div><div>Might be nice to think about a more elegant way to trigger the HTTP server when needed. Even requiring some kind of trigger file in each directory would be better than the hard-coded path rule we use now.</div>
<span class="HOEnZb"><font color="#888888"><div><br></div></font></span></div></blockquote><div><br></div><div>I'd prefer/recommend LayoutTests/imported/w3c as well (and just modify the test scripts to deal w/ the additional http servers). As you start to pull in more of the w3c's tests, there will probably need to be some overall cleanup and refactoring of how stuff like this works and is shared (e.g., duplication of files under resources/ , paths mapped in the http server, etc.). Blink has the same issues. I'd be happy to help out with this where possible to try and keep things relatively consistent.</div>
<div><br></div><div>-- Dirk</div><div><br></div></div></div></div>