New issue
Advanced search Search tips

Issue 887582 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

[VR Browsing] Automatable test cases: Chrome internal pages

Project Member Reported by dbbrooks@chromium.org, Sep 20

Issue description

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


Test cases:
1. Chrome internal pages

Test case steps:
1. Access chrome://chrome-urls on the test device
2. Enter VR Browsing
3. Click the link in the list of chrome-urls to open specific url
Verify:
    a) Chrome url is opened and rendered without any visual defects
    b) Page is scrollable and UI controls are clickable and actionable (except inputs and popups)
4. Click “Back” button in the URL bar until you get back to the list of the chrome-urls
5. Repeat steps e - g for the every single url in “chrome://chrome-urls”
6. Repeat steps with chrome://interstitials
 
Can this be done with a subset of pages? Simply loading the page and ensuring we don't crash or something would be doable, but adding interactions to each page would be time consuming with little to no benefit - the vast majority (if not all) urls just point to regular HTML pages, so any issues that pop up here should do so on normal webpages, too.
Cc: btebbs@chromium.org
+btebbs since you seem to be making a number of VRB-related decisions. Any input on what subset of URLs and interstitials we should be using?

Sign in to add a comment