Update VR latency test runner to support VrCore settings modification |
|||
Issue descriptionThe test runner used for VR motion-to-photon latency tests was originally created assuming that the test device would be properly set up beforehand and stay constant. However, now that we are also running Telemetry tests on the same device, it's possible that the VrCore settings used for motopho tests will change between runs (most notably the paired headset). The end goal would be to support the setting of VrCore preferences before running the test like Telemetry. However, this requires porting the test runner over to use Devil, which might take a bit of work to support. A quick, temporary solution would be to have the Telemetry tests apply the Cardboard settings file after they are finished so that the device is always left in the same state after a test.
,
Jul 4
,
Aug 7
Removing Internals>VR component and remapping to Internals>XR
,
Aug 7
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Oct 17 2017