New issue
Advanced search Search tips

Issue 909938 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Task
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

[WebXR on Windows] Automatable test cases: Room stage awareness

Project Member Reported by dbbrooks@chromium.org, Nov 29

Issue description

These are automatable manual test cases as determined by a manual test case review with Brian a couple weeks ago.

Manual Test cases:
1. Stage height
2. Room Stage Boundary Awareness

Test Steps for #1:
1. Set stage height in respective app (Oculus, Steam, Windows Mixed Reality) to your actual (human) height.
2. Place device on head.
    a.) Go to https://immersive-web.github.io/webxr-samples/positional-audio.html and press enter VR.
    b.)Verify floor is at an accurate height. 
3. Place device on desk.
4. Close and re-open Chrome
5. Go to https://immersive-web.github.io/webxr-samples/positional-audio.html and press enter VR.
6. Verify floor is at an accurate height. 

Test Steps for #2:

Pending creation of a new test page, see bug 909933.
 
Status: Assigned (was: Untriaged)
Labels: -Type-Bug Type-Task
Re-assigning to Bill since #1 shouldn't require any additional infrastructure work, it should just be a matter of actually writing the test. Feel free to re-assign to someone else with more spare cycles.

Since AFAIK the room stage settings are calculated based off the device-to-origin transform, we should be able to just set it like we do in an existing case and assert that the correct 6DOF coordinates are propagated to WebXR https://cs.chromium.org/chromium/src/chrome/browser/vr/webxr_vr_frame_pose_browser_test.cc?q=waitgetpresenting&sq=package:chromium&dr=CSs&l=122.

For #2, we might need a bit of additional plumbing in order to set safety bounds/stage dimensions during a test?
Cc: bsheedy@chromium.org
Owner: billorr@chromium.org
Actually re-assign to Bill.

Sign in to add a comment