Inject events into window server for telemetry tests |
||||||
Issue descriptionFor telemetry tests, the input events (e.g. mouse-wheel, touch-scroll etc.) are generated at the browser, and the latency measured is between the browser and the renderer. When running the tests with mus, it is necessary to inject the events at the window server, so that the latency from the window-server to the browser is also included in the measurement.
,
May 15 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8a7826ac6e0b8e4c18ca72ea7b03436185f199a5 commit 8a7826ac6e0b8e4c18ca72ea7b03436185f199a5 Author: sadrul <sadrul@chromium.org> Date: Mon May 15 17:04:39 2017 aura: Introduce EventInjector. Introduce EventInjector, which can be used to inject events into aura. In LOCAL mode, the events are directly injected on aura::WindowTreeHost. In MUS mode, EventInjector injects the event at the window-server using the WindowServerTest api. BUG= 721640 Review-Url: https://codereview.chromium.org/2869273010 Cr-Commit-Position: refs/heads/master@{#471806} [modify] https://crrev.com/8a7826ac6e0b8e4c18ca72ea7b03436185f199a5/content/browser/renderer_host/input/synthetic_gesture_target_aura.cc [modify] https://crrev.com/8a7826ac6e0b8e4c18ca72ea7b03436185f199a5/ui/aura/BUILD.gn [modify] https://crrev.com/8a7826ac6e0b8e4c18ca72ea7b03436185f199a5/ui/aura/env.h [add] https://crrev.com/8a7826ac6e0b8e4c18ca72ea7b03436185f199a5/ui/aura/event_injector.cc [add] https://crrev.com/8a7826ac6e0b8e4c18ca72ea7b03436185f199a5/ui/aura/event_injector.h
,
Jun 6 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/77c67de3a506c39bf84fec3f92585c507f16f29f commit 77c67de3a506c39bf84fec3f92585c507f16f29f Author: sadrul <sadrul@chromium.org> Date: Tue Jun 06 17:29:06 2017 mash: Add catalog/manifest etc. for telemetry tests binary for mash. For telemetry tests, the browser needs to get access to some test api from the mus window server, which is only exposed to clients marked as 'test' in their manifest. Instead of making default chrome-browser such a test client, create a separate telemetry-browser catalog, which is used when run with --use-test-config command-line flag. Instead of adding dependency on this test catalog from the main chrome executable, create a separate test_chrome executable that can be used for running the telemetry tests. BUG= 704681 , 721640 Review-Url: https://codereview.chromium.org/2910383002 Cr-Commit-Position: refs/heads/master@{#477326} [modify] https://crrev.com/77c67de3a506c39bf84fec3f92585c507f16f29f/chrome/BUILD.gn [modify] https://crrev.com/77c67de3a506c39bf84fec3f92585c507f16f29f/chrome/app/BUILD.gn [modify] https://crrev.com/77c67de3a506c39bf84fec3f92585c507f16f29f/chrome/app/chrome_main_delegate.cc [modify] https://crrev.com/77c67de3a506c39bf84fec3f92585c507f16f29f/chrome/app/chrome_main_delegate.h [add] https://crrev.com/77c67de3a506c39bf84fec3f92585c507f16f29f/chrome/app/chrome_test_exe_main_aura.cc [modify] https://crrev.com/77c67de3a506c39bf84fec3f92585c507f16f29f/chrome/app/mash/BUILD.gn [add] https://crrev.com/77c67de3a506c39bf84fec3f92585c507f16f29f/chrome/browser/chrome_test_browser_overlay.json
,
Jun 8 2017
,
Aug 22 2017
,
Aug 22 2017
Issue 704670 has been merged into this issue.
,
Jan 22 2018
,
Feb 26 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by sadrul@chromium.org
, May 12 2017