QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

Just a small comment, there are quite some parts already implemented, and would be beneficial to reuse those + extended part. Here is the list:

./tests/console/yast2_cmdline.pm
./tests/console/yast2_http.pm
./tests/console/yast2_lan_hostname.pm
./tests/console/yast2_rmt.pm
./tests/console/yast2_vnc.pm
./tests/console/yast2_bootloader.pm
./tests/console/yast2_nis.pm
./tests/console/yast2_i.pm
./tests/console/yast2_proxy.pm
./tests/console/yast2_clone_system.pm
./tests/console/yast2_dns_server.pm
./tests/console/yast2_nfs_client.pm
./tests/console/yast2_ntpclient.pm
./tests/console/yast2_scc.pm
./tests/console/yast2_ftp.pm
./tests/console/yast2_snapper_ncurses.pm
./tests/console/yast2_apparmor.pm
./tests/console/yast2_lan.pm
./tests/console/yast2_nfs_server.pm
./tests/console/yast2_samba.pm
./tests/console/yast2_tftp.pm
./tests/console/yast2_xinetd.pm
./tests/x11/yast2_snapper.pm
./tests/x11/network/yast2_network_use_nm.pm
./tests/x11/yast2_lan_restart_devices.pm
./tests/x11/yast2_lan_restart.pm
./tests/yast2_gui/yast2_bootloader.pm
./tests/yast2_gui/yast2_control_center.pm
./tests/yast2_gui/yast2_datetime.pm
./tests/yast2_gui/yast2_firewall.pm
./tests/yast2_gui/yast2_lang.pm
./tests/yast2_gui/yast2_network_settings.pm
./tests/yast2_gui/yast2_users.pm
./tests/yast2_gui/yast2_hostnames.pm
./tests/yast2_gui/yast2_software_management.pm

Note that qt/gtk version behaves exactly in same way as ncurses, 99% of the time shortcuts also match, so no sense to test functional part in both UIs.

@riafarov this activity is about testing of command line use of yast modules, not about ncurses/gui versions.

Added @vpelcak. @rodion if you think that we have some overlap/concurrent work, please align with Vit(test product owner) to avoid any confusions.

@rodion http://deva.suse.cz/tests/12#

Example of yast lan cli tests I implemented.
To show what we mean by these tests.

vpelcak wrote:

@rodion http://deva.suse.cz/tests/12#

Example of yast lan cli tests I implemented.
To show what we mean by these tests.

Ah, now I got it. I'm not aware of anything like this, so we are safe. But I would recommend to talk to YaST team, as they might have some tests already, which can be simply triggered in openQA. AFAIR, they had some cli integration tests.
Thanks for the explanation!

YaST team just confirmed that the test coverage from their side is minimal and we can proceed.

Most of yast2 modules have some TAP bash scripts included testing CLI.
For instance network module:

• https://github.com/yast/yast-network/blob/master/t/add-del.t
• TAP

OpenQA test module & TAP execution:

• console/yast2_cmdline.pm
• sle-15-SP1-Installer-DVD-x86_64-Build193.1-yast2_ui_devel@64bit

This is really bad approach to run upstream test within openQA by using rpmbuild. If it is enabled during the build in obs, it is not needed to be done again in openQA(in the same way).

It runs tests for yast lan module only and other yast modules are not covered.

pcervinka wrote:

This is really bad approach to run upstream test within openQA by using rpmbuild. If it is enabled during the build in obs, it is not needed to be done again in openQA(in the same way).

It runs tests for yast lan module only and other yast modules are not covered.

Checking the code. I can see that rpmbuild is executed with option -bp.

-bp    Executes  the  "%prep"  stage  from the spec file. Normally this in-
              volves unpacking the sources and applying any patches.

Therefore from the network package, it would particularly execute only this part.

%prep
%setup -n %{name}-%{version}

Thus, we can omit the rpmbuild call if it is the only problem what we can see. TAP tests are directly invoked using prove https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/console/yast2_cmdline.pm#L36.

TAP tests are not executed in OBS, AFAIK they are executed in openQA, or end users can run them on their own.