openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-06-08T11:36:34ZopenSUSE Project Management Tool
Redmine qe-yam - action #93641 (Closed): Create schedules for opensuse test suiteshttps://progress.opensuse.org/issues/936412021-06-08T11:36:34Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently, we are trying to replace the old partitioning_filesystem module with guided_setup. There are some opensuse tests that use the old partitioning and don't have a schedule. The scope of this ticket is to search which are these tests and create schedule for them. There are some tests that use partitioning_filesystem, but do not concern yast team.</p>
<p>Tumbleweed:<br>
<a href="https://openqa.opensuse.org/tests/overview?arch=&machine=&modules=partitioning_filesystem&distri=microos&distri=opensuse&version=Tumbleweed&build=20210606&groupid=1#" class="external">https://openqa.opensuse.org/tests/overview?arch=&machine=&modules=partitioning_filesystem&distri=microos&distri=opensuse&version=Tumbleweed&build=20210606&groupid=1#</a></p>
<p>Leap:<br>
<a href="https://openqa.opensuse.org/tests/overview?arch=&machine=&modules=partitioning_filesystem&distri=opensuse&version=15.3&build=160.3&groupid=50#" class="external">https://openqa.opensuse.org/tests/overview?arch=&machine=&modules=partitioning_filesystem&distri=opensuse&version=15.3&build=160.3&groupid=50#</a></p>
<p>Also check other products (like Tumbleweed Aarch64) if there are more tests.</p>
<p>This tool can be helpful: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/script/yaml_generator" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/script/yaml_generator</a></p>
qe-yam - action #93029 (Closed): Implement test module for Product selection using LibyuiClient i...https://progress.opensuse.org/issues/930292021-05-24T10:57:43Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Until now, we are using welcome module for product selection on SLE. This covers multiple scenarios, as identified in <a class="issue tracker-4 status-5 priority-4 priority-default closed child" title="action: [timeboxed:16h] Define all the test scenarios in welcome and accept_license test modules (Closed)" href="https://progress.opensuse.org/issues/88939">#88939</a>. We should separate the scenarios and create separate modules.</p>
<a name="Scope"></a>
<h2 >Scope:<a href="#Scope" class="wiki-anchor">¶</a></h2>
<p><strong>Job Groups:</strong> YaST<br>
<strong>Test Cases:</strong> #1 - Select product for installation (Please, see test cases in <a href="https://progress.opensuse.org/issues/93411" class="external">https://progress.opensuse.org/issues/93411</a>), use SLES as a product to select.</p>
<a name="Task"></a>
<h2 >Task:<a href="#Task" class="wiki-anchor">¶</a></h2>
<ol>
<li>Implement test module for the test case using <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/ui-framework-documentation.md" class="external">Page Object Model</a> and LibyuiClient;</li>
<li>Check that the proper product is installed: <code>cat /etc/os-release</code> and check NAME field;</li>
<li>Add this module to all the Test Suites where currently <strong>only project selection</strong> is made (That means: do NOT update test suites where some additional actions except product selection are made, e.g. switch keyboard or validate install source. That will be scope of another ticket).</li>
</ol>
qe-yam - action #91830 (Resolved): Investigate if a change of DH version for TLS negotiation can...https://progress.opensuse.org/issues/918302021-04-27T13:14:15Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>There is an open bug for this issue, that seems stale: <a href="https://bugzilla.opensuse.org/show_bug.cgi?id=1183082" class="external">https://bugzilla.opensuse.org/show_bug.cgi?id=1183082</a><br>
According to the developers' insight, we might need to change the TLS negotiation. We should investigate if the current test configuration makes sense or should be changed.</p>
<p>openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-remote_vnc_controller@64bit fails in<br>
<a href="https://openqa.opensuse.org/tests/1716077/modules/remote_controller/steps/19" class="external">remote_controller</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Controller performs remote installation via vnc to the target</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.opensuse.org/tests/1655743" class="external">20210303</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.opensuse.org/tests/1653115" class="external">20210302</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=remote_vnc_controller&version=Tumbleweed" class="external">latest</a></p>
qe-yam - action #91677 (Rejected): [sporadic] test fails in validate_fs_tablehttps://progress.opensuse.org/issues/916772021-04-24T19:31:25Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>We are expecting both filesystems for root and home to be xfs as instructed in the test_data, but quite frequently, btrfs is selected, thus filesystem validation fails. We should stabilize the test to select xfs on every run.</p>
<p>openQA test in scenario sle-15-SP3-Online-s390x-xfs@s390x-kvm-sle12 fails in<br>
<a href="https://openqa.suse.de/tests/5846924/modules/validate_fs_table/steps/15" class="external">validate_fs_table</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: QE Yast, QE Kernel</p>
<p>Installation test with explicit selection of "xfs" instead of default.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/5840675" class="external">176.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/5825916" class="external">174.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Online&machine=s390x-kvm-sle12&test=xfs&version=15-SP3" class="external">latest</a></p>
qe-yam - action #91350 (Closed): [timeboxed:16h][sporadic] test fails in verify_undelete_snapshotshttps://progress.opensuse.org/issues/913502021-04-19T10:19:46Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>The module fails when the system is creating a new snapshot and it is expecting it to be marked as disposable. On successful runs, the number of the created snapshot is 18 and it is marked as disposable. When the number of the snapshot is 11, it's not marked as disposable. We need to figure out if this behavior is per design and adjust the module expectations or open a bug.</p>
<p>Blind guess, if it's on powerVM only, we should check if there is any test suite executed between image is created and this test suite. Therefore we should check that there are no extra snapshots in some runs and clean them up before the test execution to have the same setup in each run.</p>
<p>openQA test in scenario sle-15-SP3-Online-ppc64le-transactional_server_snapper@ppc64le-hmc-single-disk fails in<br>
<a href="https://openqa.suse.de/tests/5840500/modules/verify_undelete_snapshots/steps/23" class="external">verify_undelete_snapshots</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Test snapper features in a transactional update server</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/5119908" class="external">95.1</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/5814802" class="external">174.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Online&machine=ppc64le-hmc-single-disk&test=transactional_server_snapper&version=15-SP3" class="external">latest</a></p>
qe-yam - action #87646 (Closed): Create autoyast test using btrfs quota limithttps://progress.opensuse.org/issues/876462021-01-12T14:55:23Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Automation test for feature : <a href="https://jira.suse.com/browse/SLE-7742" class="external">https://jira.suse.com/browse/SLE-7742</a><br>
Autoyast installation with btrfs quota limit for one or more subvolumes.</p>
<p>Autoyast syntax:<br>
<a href="https://github.com/yast/yast-storage-ng/pull/1186" class="external">https://github.com/yast/yast-storage-ng/pull/1186</a></p>
<p>Scope is tumbleweed and SLES 64bit.</p>
<p>Validate that limit was set, after installation:<br>
#btrfs subvolume list /mountpoint (in case we want to find a subvolume id)<br>
#btrfs qgroup show -pcre /mountpoint</p>
<a name="Acceptance-criteria"></a>
<h3 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h3>
<ol>
<li>btrfs quota limit is set in the autoyast profile</li>
<li>The limit is validated to be set, after installation</li>
</ol>
qe-yam - action #80272 (Closed): Adapt yast2_expert_partitioner (before: yast2_storage_ng) in ppc...https://progress.opensuse.org/issues/802722020-11-24T10:24:44Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-15-SP3-Online-x86_64-yast2_gui@64bit fails in<br>
<a href="https://openqa.suse.de/tests/5058960/modules/yast2_storage_ng/steps/21" class="external">yast2_storage_ng</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Maintainer: zluo, riafarov</p>
<p>Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.</p>
<p>We can use perl code, need just to add setup part including port forwarding.<br>
After <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11643" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11643</a> we still need to setup libyui for ppc64le and enable this test there.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/5032565" class="external">85.2</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/4965755" class="external">78.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=yast2_gui&version=15-SP3" class="external">latest</a></p>
qe-yam - action #80206 (Closed): Adjust msdos scenario for the UI changes in the Expert Partitionerhttps://progress.opensuse.org/issues/802062020-11-23T10:27:41Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>We already have code to create partition using libyui REST API, so should reuse it.<br>
Test is executed with SLES only.<br>
Also, by now all backends should work fine with REST API.</p>
<p>openQA test in scenario sle-15-SP3-Online-ppc64le-msdos@ppc64le fails in<br>
<a href="https://openqa.suse.de/tests/5049302/modules/msdos_partition_table/steps/2" class="external">msdos_partition_table</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Installation with MSDOS partition table.</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/5013874" class="external">85.2</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/4964791" class="external">78.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Online&machine=ppc64le&test=msdos&version=15-SP3" class="external">latest</a></p>
qe-yam - action #76885 (Resolved): Unit test for yast2-metapackage-handler OneClickInstallWorkerF...https://progress.opensuse.org/issues/768852020-11-02T19:10:38Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Add the following functions to the unit test for <a href="https://github.com/yast/yast-metapackage-handler/blob/master/src/modules/OneClickInstallWorkerFunctions.rb" class="external">OneClickInstallWorkerFunction.rb</a></p>
<p>DeDupe<br>
AddRepositories<br>
RemoveAddedRepositories</p>
<p><a href="https://github.com/yast/yast-metapackage-handler" class="external">https://github.com/yast/yast-metapackage-handler</a></p>
<p>Helpful links:<br>
Builtins <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/builtins.rb</a><br>
Ops <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/ops.rb</a><br>
deep_copy <a href="https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb" class="external">https://github.com/yast/yast-ruby-bindings/blob/master/src/ruby/yast/yast.rb</a><br>
PackageSlideShow <a href="https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb" class="external">https://github.com/yast/yast-packager/blob/master/src/modules/PackageSlideShow.rb</a><br>
Progress <a href="https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/wizard/src/modules/Progress.rb</a><br>
SlideShow <a href="https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb" class="external">https://github.com/yast/yast-yast2/blob/master/library/packages/src/modules/SlideShow.rb</a></p>
<p>See previous PRs for progress of unit testing coverage: <a href="https://github.com/yast/yast-metapackage-handler/pull/23" class="external">https://github.com/yast/yast-metapackage-handler/pull/23</a></p>
qe-yam - action #75424 (Closed): [sporadic] test fails in force_scheduled_tasks https://progress.opensuse.org/issues/754242020-10-27T20:16:16Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>Full medium test suites skip_registration and allmodules+allpatterns+registration fail sporadically for aarch64 in force_scheduled_tasks. The module is running in a loop:</p>
<pre><code>read load dummy < /proc/loadavg ; top -n1 -b| head -n30 ; test "${load/./}" -lt $limit && break ;
</code></pre>
<p>and is expected to be finished in 1005 seconds, but it times out.<br>
In all failures spotted so far, the serial returned the same output at the moment of timeout </p>
<pre><code>BTRFS info (device vda2): qgroup scan completed (inconsistency flag cleared)
</code></pre>
<p>so there could be some BTRFS inconsistency that is taking too long to be dealt with by the system.</p>
<p>As we cannot run proper performance tests and goal of the module is to improve stability of the tests.</p>
<p>failures:<br>
<a href="https://openqa.suse.de/tests/4893533/modules/force_scheduled_tasks/steps/6" class="external">allmodules+allpatterns+registration</a><br>
<a href="https://openqa.suse.de/tests/4893537#next_previous" class="external">skip_registration</a></p>
<p>Fails since (at least) Build <a href="https://openqa.suse.de/tests/4879296" class="external">67.1</a> </p>
<p><a href="https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Full&machine=aarch64&test=allmodules%2Ballpatterns%2Bregistration&version=15-SP3" class="external">latest allmodules+allpatterns+registration</a><br>
<a href="https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Full&machine=aarch64&test=skip_registration&version=15-SP3" class="external">latest skip_registration</a></p>
qe-yam - action #73477 (Closed): Modify firstboot configuration for yast2_firstboot_customhttps://progress.opensuse.org/issues/734772020-10-18T12:46:33Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In order to extend coverage for yast2-firstboot, and given that we already have 2 test suites that verify the default configuration, we can modify yast2_firstboot_custom test suite. </p>
<p>Replace /etc/sysconfig/firstboot and /etc/YaST2/firstboot.xml files in order for the firstboot to:</p>
<ul>
<li>Display customized welcome message.</li>
<li>Display customized license.</li>
<li>Display customized finish text.</li>
<li>Set autologin checked by default for new user (in case we can change default value).</li>
<li>SHOW_Y2CC_CHECKBOX="yes", which enable yast2 control center after first boot configuration (this check is low prio and can be postponed as window cannot be easily closed)</li>
</ul>
<p>before proceeding to firstboot configuration, abort and reboot in order to verify that abort button doesn't cause crash and that firstboot will run again, if not completed.</p>
<p>Relevant bugs: <a href="https://bugzilla.suse.com/show_bug.cgi?id=1161048" class="external">bug#1161048</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1177797" class="external">bug#1177797</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1076798" class="external">bug#1076798</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=950335" class="external">bug#950335</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1173498" class="external">bug#1173498</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=615146" class="external">bug#615146</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1161045" class="external">bug#1161045</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1177757" class="external">bug#1177757</a></p>
qe-yam - action #73474 (Closed): Add more modules to yast2_firstboothttps://progress.opensuse.org/issues/734742020-10-18T12:17:38Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>In order to extend coverage for yast2-firstboot , we can modify the yast2-firstboot configuration files of the relevant test suite:<br>
<a href="https://openqa.suse.de/tests/4840750" class="external">https://openqa.suse.de/tests/4840750</a></p>
<p>There already is customized file replacing /etc/YaST2/firstboot.xml after merge of:<br>
<a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10856" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10856</a></p>
<p>We should re-use yast2_firstboot_custom and use non-default settings for the modules if those are allowed.</p>
<p>Enable firstboot_ntp, firstboot_keyboard and inst_lan modules.</p>
<p>related bugs: <a href="https://bugzilla.suse.com/show_bug.cgi?id=1177797" class="external">bug#1177797</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=960081" class="external">bug#960081</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1140199" class="external">bug#1140199</a> , <a href="https://bugzilla.suse.com/show_bug.cgi?id=1101514" class="external">bug#1101514</a></p>
qe-yam - action #73471 (Closed): Enable yast2_firstboot in textmodehttps://progress.opensuse.org/issues/734712020-10-18T11:43:20Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Currently, we don't have any test for yast2-firstfoot in textmode. </p>
<p>yast2_firstboot test suite:<br>
<a href="https://openqa.suse.de/tests/5248378#step/yast2_firstboot/6" class="external">https://openqa.suse.de/tests/5248378#step/yast2_firstboot/6</a></p>
<p>should be able to run if booted in textmode hdd.</p>
<p>New needles will be needed and possibly some adjustments in the code.</p>
<p>consider to add the default scenario or the custom one or both in textmode.</p>
qe-yam - action #73096 (Rejected): [sporadic] msdos test fails in validate_fs_tablehttps://progress.opensuse.org/issues/730962020-10-07T15:14:47Zsyrianidou_sofiasofia.syrianidou@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>During msdos partitioning, the home partition is selected to be created with UDF instead of xfs filesystem. Even though, the screen matches at xfs, there is an extra key sent and the result is that home filesystem is UDF and the filesystem validation fails:</p>
<p>openQA test in scenario sle-15-SP3-Online-x86_64-msdos@svirt-xen-pv fails in<br>
<a href="https://openqa.suse.de/tests/4787764/modules/validate_fs_table/steps/28" class="external">validate_fs_table</a></p>
<p>Similar behavior has been seen before for SWAP partition but was not investigated:<br>
<a href="https://progress.opensuse.org/issues/71638" class="external">https://progress.opensuse.org/issues/71638</a></p>
<p>So we should stabilize test execution that we do not end up sending one extra key press, after wanted filesystem is selected.</p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.suse.de/tests/4780316" class="external">51.1</a> (or more recent)</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=svirt-xen-pv&test=msdos&version=15-SP3" class="external">latest</a></p>
qe-yam - action #71116 (Closed): [y] Add OpenQA test for OneClickInstallhttps://progress.opensuse.org/issues/711162020-09-08T16:03:45Zsyrianidou_sofiasofia.syrianidou@suse.com
<p>Packages can be installed via .YMP files that contain the necessary information in XML form, using OneclickInstall.<br>
As root run<br>
#OneClickInstallCLI <br>
and verify that the package is installed successfully. Accordingly, test the OneClickInstall UI<br>
#OneClickInstallUI </p>
<p>YMP URL example: <a href="https://software.opensuse.org/ymp/openSUSE:Factory/standard/vim.ymp?base=openSUSE%3AFactory&query=vim" class="external">https://software.opensuse.org/ymp/openSUSE:Factory/standard/vim.ymp?base=openSUSE%3AFactory&query=vim</a></p>
<p>The test can run on both SLE and Tumbleweed, but with different YMP URLs, but only 64-bit for a start.</p>