Create enterprise-enable-zero-touch-enrollment OOBE End-To-End test |
|||||||
Issue descriptionWe need a test that will catch b/112431049 . 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 EE cases. We need to add another test "OobeInteractiveUITest.ZeroTouchEnrollment" that will make sure ZeroTouchEnrollment starts correctly. 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. In case of zero-touch we probably need to make sure Zero-Touch process starts correctly and OOBE does not break it.
,
Sep 14
Hey Yves/Denis - can you guys work together to make sure we get adequate test coverage for this flow?
,
Sep 14
,
Oct 11
I can help validate the tests but I am no UI person so I'd like Denis to be on point for that. Denis, is it easier if I assign the bug to you? I will be in the Munich office 10/26-10/30, can you (antrim@) take a stab at what you want to do before that and we can meet and review (or write the test and we can meet and review)? Thanks!
,
Nov 8
The ZT flow seems pretty broken right now. After an error trying to get an enrollment certificate, the screen "Enterprise Enrollment / Enrolling device..." is still shown instead of an error. Logs show that the error was reported: [1491:1491:1108/125154.189156:VERBOSE1:wizard_controller.cc(2102)] Showing enrollment screen. Forcing interactive enrollment: 0. [1491:1491:1108/125154.189184:VERBOSE1:wizard_controller.cc(1370)] SetCurrentScreenSmooth: oauth-enrollment [1491:1491:1108/125154.189871:VERBOSE1:enrollment_screen.cc(219)] Authenticating using attestation. [1491:1491:1108/125154.190771:ERROR:attestation_flow.cc(47)] Attestation: Failed to check enrollment state. [1491:1491:1108/125154.190795:WARNING:enrollment_handler_chromeos.cc(832)] Enrollment failed: 15, client: 0, validation: 0, store: 0, lock: 0 [1491:1491:1108/125154.190917:WARNING:enrollment_screen_handler.cc(673)] EnrollmentScreenHandler::UpdateState(): state=online, reason=update localhost ~ #
,
Nov 13
,
Nov 23
The problem is that OobeInteractiveUITest.SimpleEndToEnd is too flaky and it was disabled.
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by alemate@chromium.org
, Sep 13