<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 6, 2017, at 5:15 PM, Alexey Proskuryakov <<a href="mailto:ap@webkit.org" class="">ap@webkit.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">6 февр. 2017 г., в 12:28, Ryosuke Niwa <<a href="mailto:rniwa@webkit.org" class="">rniwa@webkit.org</a>> написал(а):</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">The concern I've heard about is not how run-webkit-tests run the tests. It's about how a test is opened inside a browser, DRT, WTR while debugging.</div></div></blockquote><br class=""></div><div class="">+1</div><div class=""><br class=""></div><div class="">I think that making web platform tests more practical for engineers to work with should be a pre-requisite for deeper integration.</div><div class=""><br class=""></div><div class="">From tools perspective, cleaning up the way we get supporting scripts for web platform tests would be quite beneficial too. It is very hard to reason about what happens in a merge that just updates .tar.gz files or a SHA hash.</div></div></div></blockquote></div><br class=""><div class="">I think the potential of more automated sync and two-way sync with Web Platform Tests is great.</div><div class=""><br class=""></div><div class="">I also agree with Alexey and Ryosuke. It needs to be easy to run this type of test, including loading it in the browser. And managing the merge should not impose extra burdens on the person developing a patch. Our regression test requirement already imposes a significant (but important!) burden and we shouldn't make it worse.</div><div class=""><br class=""></div><div class="">The extra work should be done either by an automated system or by a person who is focused on doing periodic merges.</div><div class=""><br class=""></div><div class=""> - Maciej</div></body></html>