Changeset View
Changeset View
Standalone View
Standalone View
neon/tests/install_ubiquity.pm
| Show First 20 Lines • Show All 43 Lines • ▼ Show 20 Line(s) | 23 | sub run { | |||
|---|---|---|---|---|---|
| 44 | assert_screen "installer-welcome", 60; | 44 | assert_screen "installer-welcome", 60; | ||
| 45 | if (get_var('OPENQA_INSTALLATION_NONENGLISH')) { | 45 | if (get_var('OPENQA_INSTALLATION_NONENGLISH')) { | ||
| 46 | assert_and_click 'installer-welcome-click'; | 46 | assert_and_click 'installer-welcome-click'; | ||
| 47 | send_key 'down'; | 47 | send_key 'down'; | ||
| 48 | send_key 'ret'; | 48 | send_key 'ret'; | ||
| 49 | assert_screen 'installer-welcome-espanol'; | 49 | assert_screen 'installer-welcome-espanol'; | ||
| 50 | } | 50 | } | ||
| 51 | assert_and_click "installer-next"; | 51 | assert_and_click "installer-next"; | ||
| 52 | | ||||
| 53 | # bionic version of ubiquity moved the keyboard configuration as first step | ||||
sitter: comment on why this is necessary please. ideally with ticket/bug uri for fixing this in the… | |||||
| 54 | if (testapi::get_var('OPENQA_SERIES') eq 'bionic') { | ||||
should probably be ne 'xenial', seeing as this is the new default moving forward. So this also applies to 20.04 most likely sitter: should probably be `ne 'xenial'`, seeing as this is the new default moving forward. So this… | |||||
| 55 | assert_screen "installer-keyboard", 16; | ||||
| 56 | record_soft_failure 'https://phabricator.kde.org/T9236'; | ||||
| 57 | assert_and_click "installer-next"; | ||||
| 58 | } | ||||
| 59 | | ||||
| 52 | assert_screen "installer-prepare", 16; | 60 | assert_screen "installer-prepare", 16; | ||
| 53 | assert_and_click "installer-next"; | 61 | assert_and_click "installer-next"; | ||
| 54 | assert_screen "installer-disk", 16; | 62 | assert_screen "installer-disk", 16; | ||
| 55 | assert_and_click "installer-install-now"; | 63 | assert_and_click "installer-install-now"; | ||
| 56 | assert_and_click "installer-disk-confirm", 'left', 16; | 64 | assert_and_click "installer-disk-confirm", 'left', 16; | ||
| 57 | 65 | | |||
| 58 | # Timezone has 75% fuzzyness as timezone is geoip'd so its fairly divergent. | 66 | # Timezone has 75% fuzzyness as timezone is geoip'd so its fairly divergent. | ||
| 59 | # Also, starting here only the top section of the window gets matched as | 67 | # Also, starting here only the top section of the window gets matched as | ||
| 60 | # the bottom part with the buttons now has a progressbar and status | 68 | # the bottom part with the buttons now has a progressbar and status | ||
| 61 | # text which is non-deterministic. | 69 | # text which is non-deterministic. | ||
| 62 | # NB: we give way more leeway on the new needle appearing as disk IO can | 70 | # NB: we give way more leeway on the new needle appearing as disk IO can | ||
| 63 | # cause quite a bit of slowdown and ubiquity's transition policy is | 71 | # cause quite a bit of slowdown and ubiquity's transition policy is | ||
| 64 | # fairly weird when moving away from the disk page. | 72 | # fairly weird when moving away from the disk page. | ||
| 65 | assert_screen "installer-timezone", 60; | 73 | assert_screen "installer-timezone", 60; | ||
| 66 | assert_and_click "installer-next"; | 74 | assert_and_click "installer-next"; | ||
| 75 | | ||||
| 76 | # bionic version of ubiquity moved the keyboard configuration as first step | ||||
| 77 | # while in xenial version the keyboard config is after timezone setup | ||||
| 78 | if (testapi::get_var('OPENQA_SERIES') eq 'xenial') { | ||||
| 67 | assert_screen "installer-keyboard", 16; | 79 | assert_screen "installer-keyboard", 16; | ||
| 80 | record_soft_failure 'https://phabricator.kde.org/T9236'; | ||||
| 68 | assert_and_click "installer-next"; | 81 | assert_and_click "installer-next"; | ||
| 69 | 82 | } | |||
comment on why this is necessary please. ideally with ticket/bug uri for fixing this in the long run. sitter: comment on why this is necessary please. ideally with ticket/bug uri for fixing this in the… | |||||
| 70 | assert_screen "installer-user", 16; | 83 | assert_screen "installer-user", 16; | ||
| 71 | type_string $user; | 84 | type_string $user; | ||
| 72 | # user in user field, name field (needle doesn't include hostname in match) | 85 | # user in user field, name field (needle doesn't include hostname in match) | ||
| 73 | assert_screen "installer-user-user", 16; | 86 | assert_screen "installer-user-user", 16; | ||
| 74 | send_key "tab", 1; # username field | 87 | send_key "tab", 1; # username field | ||
| 75 | send_key "tab", 1; # 1st password field | 88 | send_key "tab", 1; # 1st password field | ||
| 76 | type_string $password; | 89 | type_string $password; | ||
| 77 | send_key "tab", 1; # 2nd password field | 90 | send_key "tab", 1; # 2nd password field | ||
| 78 | type_string $password; | 91 | type_string $password; | ||
| 79 | # all fields filled (not matching hostname field) | 92 | # all fields filled (not matching hostname field) | ||
| 80 | assert_screen "installer-user-complete", 16; | 93 | assert_screen "installer-user-complete", 16; | ||
| 81 | assert_and_click "installer-next"; | 94 | assert_and_click "installer-next"; | ||
| 82 | 95 | | |||
| 83 | assert_screen "installer-show", 10; | 96 | assert_screen "installer-show", 15; | ||
sitter: reason? | |||||
Because slideshow had some timing issue or something. I think at first occurrence of slideshow image it didn't match it, so had to give it bit of headroom bshah: Because slideshow had some timing issue or something. I think at first occurrence of slideshow… | |||||
| 84 | 97 | | |||
| 85 | # Let install finish and restart | 98 | # Let install finish and restart | ||
| 86 | assert_screen "installer-restart", 640; | 99 | assert_screen "installer-restart", 640; | ||
| 87 | assert_and_click "installer-restart-now"; | 100 | assert_and_click "installer-restart-now"; | ||
| 88 | 101 | | |||
| 89 | assert_screen "live-remove-medium", 60; | 102 | assert_screen "live-remove-medium", 60; | ||
| 90 | # The message actually comes up before input is read, make sure to send rets | 103 | # The message actually comes up before input is read, make sure to send rets | ||
| 91 | # until the system reboots or we've waited a bit of time. We'll then | 104 | # until the system reboots or we've waited a bit of time. We'll then | ||
| Show All 36 Lines | |||||
comment on why this is necessary please. ideally with ticket/bug uri for fixing this in the long run.
also, please record_soft_failure with the ticket/bug or some description.