![]() ![]() Where necessary, GPU-specific results are maintained for these tests. ![]() Using the full browser to execute tests, rather than smaller test harnesses, has yielded several advantages: testing what is shipped, improved reliability, and improved performance.Ī subset of the tests, called “pixel tests”, grab screen snapshots of the web page in order to validate Chromium's rendering architecture end-to-end. The GPU bots launch the full Chromium browser via Telemetry for the majority of the tests. Telemetry directs the browser to perform various operations, like page navigation and test execution, from external scripts written in Python. ![]() Telemetry was originally conceived as a performance testing framework, but has proven valuable for correctness testing as well. Most of the tests on the GPU bots are run via the Telemetry framework. The GPU bots specifically focus on tests which exercise the graphics processor, and whose results are likely to vary between graphics card vendors. The GPU bots run a different set of tests than the majority of the Chromium test machines. Updating and Adding New Pixel Tests to the GPU Bots.Debugging Pixel Test Failures on the GPU Bots.Adding a new test to one of the existing test harnesses.Moving Test Binaries from Machine to Machine.Running Locally Built Binaries on the GPU Bots.Debugging a Specific Subset of Tests on a Specific GPU Bot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |