> Another concern is the ease of running tests for developers: drag&dropping > tests into a browser instead of running a server.
Yeah, it’s a pretty big concern if you can’t just drop a simple test case into a browser. > We can partially accommodate this by rewriting > testharness.js/testharnessreport.js urls. > A significant and growing amount of wpt tests will not behave as expected > (other resources loaded, origins, need for specific headers, need for https…) This might be a reason to prefer WPT tests when you know you’re testing something whose behavior depends on http. But in all other cases, the ability for a test to be a self-contained file that can run in any browser, upload to a bug tracker, and so on, is super valuable. Geoff _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
