New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 883980 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 880803



Sign in to add a comment

Create OOBE end-to-end test with ARC++ screens.

Project Member Reported by alemate@chromium.org, Sep 13

Issue description

We have full OOBE end-to-end test "OobeInteractiveUITest.SimpleEndToEnd": https://cs.chromium.org/chromium/src/chrome/browser/chromeos/login/oobe_interactive_ui_test.cc?l=260 which verifies all OOBE steps including First Run UI (and makes sure it is closed at the end).

But it does not cover ARC++-specific screens. We need to add another test "OobeInteractiveUITest.WithARCEnabled" that will go through the all screens, including ARC++ ones. Basically we need to copy "SimpleEndToEnd" and enable ARC++.

The goal is to verify that our OOBE + First Run flow is correctly displayed, and can be correctly navigated through. (And that dependencies are resolved correctly). We do not need to test too much of the functionality of the individual screens/dialogs, but some basic checks are very welcome (see existing checks).

Feel free to add as many First run flows as you can ;)
 
Cc: zalcorn@chromium.org
Assigning to Elijah for triage.
Components: UI>Shell>OOBE
Cc: lgcheng@chromium.org jhorwich@chromium.org
Components: Platform>Apps>ARC
Owner: ----
Status: Available (was: Untriaged)
Labels: M-72

Sign in to add a comment