coordination #27074
Updated by okurz about 6 years ago
## Motivation Even with a workaround (yast2 call with --qt) we still have problem with all yast2 gui tests. This could be issue with product change (layout, fonts) or something else. As a QA engineer I want to see valid test results for yast2 gui test suite. We need adjustments for all tests modules which verify yast2 qt modules. For most of them it should include only new set of needles, for some it may need minor code adjustment. ## Acceptance criteria criteria: * **AC1:** **AC1** All test modules either are successful or fail due to product bug * **AC2:** **AC2** All test modules are adjusted according AC1 both for leap and sle (assuming TW is not affected) ## Further details Latest links to yast2_gui and yast2_ncurses tests: * [SLE yast2_gui](http://openqa.suse.de/tests?match=yast2_gui) * [SLE yast2_ncurses](http://openqa.suse.de/tests?match=yast2_ncurses) * [openSUSE yast2_gui](http://openqa.opensuse.org/tests?match=yast2_gui) * [openSUSE yast2_ncurses](http://openqa.opensuse.org/tests?match=yast2_ncurses)