coordination #23864: [sle][functional][sle15][epic] all needles for yast2_gui test need to replaced because of product changes - openQA Tests (public) - openSUSE Project Management Tool

Actions

Copy link

coordination #23864

closed

[sle][functional][sle15][epic] all needles for yast2_gui test need to replaced because of product changes

Added by zluo over 7 years ago. Updated about 4 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Bugs in existing tests

Target version:

openQA Project (public) - Milestone 12

Start date:

2017-09-28

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

Difficulty:

Description

https://openqa.suse.de/tests/1138787
GTK is not used for sles 15, it uses QT as TW. That is why all yast2_gui tests got failed

We have to create new needles for yast_gui tests.

Subtasks 3 (0 open — 3 closed)

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by zluo over 7 years ago

Related to coordination #23820: [sle][functional][sle15][epic]update yast2_ui for sle15 added

Actions

Copy link

Updated by zluo over 7 years ago

just give here a list for yast2_gui tests:

yast2_control_center
yast_bootloader
yast2_datetime
yast2_firewall
yast2_hostnames
yast2_lang
yast2_network_settings
yast2_software_management
yast2_users

Actions

Copy link

Updated by okurz over 7 years ago

Has duplicate action #23862: sles 15 - all needles for yast2_gui test need to replaced because product changes added

Actions

Copy link

Updated by zluo over 7 years ago

Has duplicate deleted (action #23862: sles 15 - all needles for yast2_gui test need to replaced because product changes)

Actions

Copy link

Updated by zluo over 7 years ago

I found gnome-screenlock issue: bsc#1058521
this seems to block further yast2 gui tests.

Actions

Copy link

Updated by zluo over 7 years ago

Status changed from New to In Progress
Assignee set to zluo

Actions

Copy link

Updated by okurz over 7 years ago

Status changed from In Progress to Feedback

I think the bug will not be easy to be solved because there is not so much information but I agree that we are basically blocked by this issue. I labeled the last yast_ui test https://openqa.suse.de/tests/1168210 with this bug so we can for now wait for the bug to be resolved unless we want to implement a workaround which I don't see as necessary right now -> feedback

Actions

Copy link

Updated by zluo over 7 years ago

I checked the latest run of yast2_ui:
http://openqa.suse.de/tests/1173502#
consoletest_finish got passed, but we still have a production issue:

https://bugzilla.suse.com/show_bug.cgi?id=1059071

yast2 cannot be launched in QT mode. This blocks yast2 gui tests.

Actions

Copy link

Updated by zluo over 7 years ago

Related to deleted (coordination #23820: [sle][functional][sle15][epic]update yast2_ui for sle15)

Actions

Copy link

#10

Updated by zluo over 7 years ago

Blocks coordination #23820: [sle][functional][sle15][epic]update yast2_ui for sle15 added

Actions

Copy link

#11

Updated by okurz over 7 years ago

Status changed from Feedback to In Progress

build 264.3 shows the yast2 UI to start up based on Qt so I recommend to needle all with the use of interactive mode. I was wrong to assume that the interactive mode with caching workers works again even though it worked for me in between. Must have been a custom hotpatched worker. szarate will focus on getting the interactive mode on shared workers fixed in our production environment. I tried to do it locally on lord.arch but failed to do so because of another problem that is preventing me from using lord.arch for any x86_64 tests relying on assert_and_click. So please use your own local worker with interactive needling to update the UI. If this also does not work for you I recommend to delegate the issue to someone else who has a usable setup or we wait until any of us two can use openQA + interactive mode for needling.

Actions

Copy link

#12

Updated by zluo over 7 years ago

PR new needles for yast2_lang.pm
https://gitlab.suse.de/openqa/os-autoinst-needles-sles/merge_requests/497

Actions

Copy link

#13

Updated by okurz about 7 years ago

Subject changed from sles 15 - all needles for yast2_gui test need to replaced because of product changes to [sle][functional][sle15] all needles for yast2_gui test need to replaced because of product changes
Due date set to 2017-10-11
Target version set to Milestone 11

Actions

Copy link

#14

Updated by okurz about 7 years ago

Status changed from In Progress to Feedback

again blocked by product either never reaching the point of yast2_gui or being blocked by yast2_gui specific bugs. -> on feedback until we have resolved at least https://bugzilla.suse.com/show_bug.cgi?id=1062733

Actions

Copy link

#15

Updated by okurz about 7 years ago

Subject changed from [sle][functional][sle15] all needles for yast2_gui test need to replaced because of product changes to [sle][functional][sle15][epic] all needles for yast2_gui test need to replaced because of product changes
Status changed from Feedback to In Progress
Assignee deleted (~~zluo~~)
Target version changed from Milestone 11 to Milestone 12

It seems we have too many "yast2_gui needle update" tickets again which we should sort out. We have a workaround to apply the right UI framework to be applied for the test so I assume a solution should be as simple as cloning the latest job and using the interactive mode to update all needles accordingly which we should definitely be able to accomplish in the next milestone. Unfortunately can't schedule it for the next sprint directly as it has subtasks, therefore adding [epic] keyword.

Actions

Copy link

#16