Weizhong Xia
Weizhong Xia
Currently wptrunner is running different type of tests in different rounds. At the end of each round there will be time spent to wait for all workers to finish. With...
This would save approximately 0.5 second on each test runner restarts. And this should not cause a problem as another connection to the webdriver will be made to init the...
Currently chromium's WPT exporter is exporting PRs in draft mode, and change it to ready until it is ready to land. To not run tests for PRs in draft mode...
Do not restart browser when test type changes At least for Chrome, parameters used to start Chrome won't change when test type changes. This change tries to switch to a...
There are some exceptions thrown in testdriver-extra.js [1]. As the exceptions are thrown inside the browser, will they cause test to fail [1] https://source.chromium.org/search?q=f:third_party%2Fwpt_tools%2Fwpt%2Ftools%2Fwptrunner%2Fwptrunner%2Ftestdriver-extra.js%20%22throw%20new%22&ss=chromium%2Fchromium%2Fsrc
To run WPTs locally, developers usually only run a few of tests each time. Updating WPT manifest for the whole WPT Repo is not necessary and took ~3 seconds on...
As we will need to restart the browser when starting a new subsuite, putting tests in one group can help reduce the number of restarts needed. Keep an up limit...
When run WPTs locally, we (at least at google) always update the WPT Manifest to make sure the test is run correctly (e.g. to make sure Wptrunner view the the...
See the results on [wpt.fyi](https://wpt.fyi/results/fenced-frame?label=master&label=experimental&aligned), and the discussion in chromium [bug](https://g-issues.chromium.org/issues/366257368). Looks like the cross browsing context communication is supported through [RFC 98](https://github.com/web-platform-tests/rfcs/blob/master/rfcs/remote_channel.md), but use that with test driver is...