New issue
Advanced search Search tips

Issue 737182 link

Starred by 2 users
Status: WontFix
Owner:
bsheedy@chromium.org
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Task
Proj-XR



Sign in to add a comment

Possibly move VR perf tests over to established test runner

Project Member Reported by bsheedy@chromium.org, Jun 27 2017 
Right now, the perf tests in https://cs.chromium.org/chromium/src/chrome/test/vr/perf/?q=chrome/test/vr/perf+package:%5Echromium$&dr do everything on their own such as device setup. If possible, it would be good to move these to an existing test runner such as https://cs.chromium.org/chromium/src/build/android/test_runner.py so we can re-use code and get access to things like the constant for the path to the source checkout root.

Comment 1 by bsheedy@chromium.org, Oct 16 2017

Status: WontFix (was: Assigned)
I'm going to go ahead and close this since making the tests run using the Android test runner doesn't make sense (that's meant for things like instrumentation tests), and when we talked previously to nednguyen@ about making them Telemetry tests, the consensus was that they're too different to fit neatly in as one.

Issue 772969 does cover the desire to switch the tests over to using Devil instead of the somewhat hacky approach we do now, though.

Comment 2 by btebbs@chromium.org, Jul 4

Components: Blink>WebXR
►

Sign in to add a comment