openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-02-01T16:50:31ZopenSUSE Project Management Tool
Redmine openQA Tests - action #47012 (Resolved): [functional][u] Summary or Maintainer info missing from ...https://progress.opensuse.org/issues/470122019-02-01T16:50:31Zagraulalexander.graul@suse.com
<p>There are quite a few test module that don't have maintainer or summary metadata.</p>
<p>os-autoinst-distri-opensuse's travis ci checks that all touched test modules in a commit have that metadata, not just for new test modules. This causes <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6586" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6586</a> to fail the CI, since that PR touches a lot of files and some of them don't have the metadata present.</p>
<p>I've attached the list of all test modules in os-autoinst-distri-opensuse that fail the check as of now.</p>
openQA Tests - action #45653 (Resolved): [functional][y] Improve yast2_hostnames testhttps://progress.opensuse.org/issues/456532019-01-02T15:03:34Zagraulalexander.graul@suse.com
<p>As the last step of <a href="https://progress.opensuse.org/issues/41873" class="external">https://progress.opensuse.org/issues/41873</a>, the test module for the hostnames needs to be improved. The current test does not include any verification of added / changed entries are written back into /etc/hosts. While this is already covered by unittests from the yast developers, an integration check inside the products should exist to verify the module is useful for a user.</p>
openQA Project - action #44465 (New): Webui shows one test module but worker starts a different onehttps://progress.opensuse.org/issues/444652018-11-28T16:25:04Zagraulalexander.graul@suse.com
<p>I have two versions of one test module: one in /var/lib/openqa and one in /openqa-share. The latter is an NFS mount and specified as SHARE_DIRECTORY in my workers.ini (attached). The webui displays the one from /openqa-share [0], but a different on is executed [1]. The module in /var/lib/openqa (attached) includes "grep 127.0.0.1 /etc/hosts" while that line is different in the /openqa-share one. I edited the test case in /openqa-share before starting a new run.</p>
<p>[0] - <a href="http://agraul-vm.qa.suse.de/tests/18/modules/yast2_hostnames/steps/1/src" class="external">http://agraul-vm.qa.suse.de/tests/18/modules/yast2_hostnames/steps/1/src</a><br>
[1] - <a href="http://agraul-vm.qa.suse.de/tests/18#step/yast2_hostnames/16" class="external">http://agraul-vm.qa.suse.de/tests/18#step/yast2_hostnames/16</a></p>
openQA Tests - action #44027 (Resolved): [functional][y] Investigate and improve yast hostnames u...https://progress.opensuse.org/issues/440272018-11-20T10:28:45Zagraulalexander.graul@suse.com
<p>Check how much of the test plan is already covered and how it can be improved, then implement those changes.</p>
openQA Tests - action #41855 (Resolved): [functional][y] Develop test plan for yast2_hostnames fr...https://progress.opensuse.org/issues/418552018-10-01T09:00:03Zagraulalexander.graul@suse.com
<a name="YaST-Hostnames-Module-test-plan"></a>
<h1 >YaST Hostnames Module test plan<a href="#YaST-Hostnames-Module-test-plan" class="wiki-anchor">¶</a></h1>
<a name="Introduction"></a>
<h2 >Introduction<a href="#Introduction" class="wiki-anchor">¶</a></h2>
<p>YaST Hostnames is a module that helps system administrators with configuring<br>
their <code>/etc/hosts</code> file. It has a Terminal and a Graphical User Interface and<br>
validates input.</p>
<a name="Features-to-be-Tested"></a>
<h2 >Features to be Tested<a href="#Features-to-be-Tested" class="wiki-anchor">¶</a></h2>
<a name="Included"></a>
<h3 >Included<a href="#Included" class="wiki-anchor">¶</a></h3>
<ul>
<li>Terminal UI</li>
<li>Graphical UI</li>
<li>File reading + parsing</li>
<li>File saving</li>
<li>Input validation</li>
<li>Aborting without damaging the existing content</li>
</ul>
<a name="Excluded"></a>
<h3 >Excluded<a href="#Excluded" class="wiki-anchor">¶</a></h3>
<ul>
<li>Ease of use</li>
<li>Performance</li>
<li>Handling of large files (exact metric is not decided yet)</li>
</ul>
<a name="Test-Strategy"></a>
<h2 >Test Strategy<a href="#Test-Strategy" class="wiki-anchor">¶</a></h2>
<p>The most important component is that saving the configuration creates a working<br>
file, i.e. it is not corrupted or damaged. It is equally important that<br>
cancellation keeps the old configuration intact. Therefore the biggest focus is<br>
on disk IO.<br>
Functionality only needs to be tested once, one of the two UIs is used to test<br>
the functionality while the other is just checked for visual correctness.<br>
Input validation, correct parsing of existing <code>/etc/hosts</code> file and aborting is<br>
tested in the GUI, while the TUI only needs to render correctly and have working<br>
keyboard shortcuts.</p>
<p>Test cases 1 and 2 will be executed on ARM, Power.<br>
All test cases will be executed on x86_64, using Qt GUI on GNOME (Xorg).<br>
Additionally, test case 5 is executed using the ncurses TUI and Qt on GNOME<br>
(Wayland).<br>
On s390, only ncurses is used as UI in the tests.</p>