openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-05-07T03:03:45ZopenSUSE Project Management Tool
Redmine openQA Tests - action #51212 (Resolved): [sle12sp5][desktop] test fails in wiresharkhttps://progress.opensuse.org/issues/512122019-05-07T03:03:45Zyfjiangyfjiang@suse.com
<p>Wireshark test cases in sled-12-sp5 and sles-12-sp5-we are failed in openQA without exception, e.g. :</p>
<p><a href="https://openqa.suse.de/tests/2864383#step/wireshark/62" class="external">https://openqa.suse.de/tests/2864383#step/wireshark/62</a><br>
<a href="https://openqa.suse.de/tests/2865731#step/wireshark/62" class="external">https://openqa.suse.de/tests/2865731#step/wireshark/62</a></p>
<p>A recent release of wireshark security version update maybe worthy of noticing:</p>
<p><a href="https://maintenance.suse.de/request/190354" class="external">https://maintenance.suse.de/request/190354</a></p>
openQA Tests - action #49733 (Rejected): [sle12sp5][desktop] test fails in welcomehttps://progress.opensuse.org/issues/497332019-03-27T08:22:59Zyfjiangyfjiang@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>openQA test in scenario sle-12-SP5-Desktop-MINI-ISO-x86_64-remote_vnc_controller_sled@64bit fails in<br>
<a href="https://openqa.nue.suse.com/tests/2741587/modules/welcome/steps/5" class="external">welcome</a></p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Install remote server (parallel job) with vnc.</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.nue.suse.com/tests/2738028" class="external">0116</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.nue.suse.com/tests/2521466" class="external">0112</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.nue.suse.com/tests/latest?test=remote_vnc_controller_sled&machine=64bit&version=12-SP5&flavor=Desktop-MINI-ISO&arch=x86_64&distri=sle" class="external">latest</a></p>
openQA Tests - action #37808 (Resolved): [sle15sp1][desktop] Enable gnome-message testing.https://progress.opensuse.org/issues/378082018-06-26T04:20:37Zyfjiangyfjiang@suse.com
<p>The messaging group contains pidgin and evolution testing which need to be enabled in sle15sp1.</p>
<p>To avoid duplication effort, I kept here that QAM colleagues are working on at the moment, see related tickets</p>
openQA Tests - action #37027 (Resolved): [tw][desktop] Update create_hdd_* to make sure right per...https://progress.opensuse.org/issues/370272018-06-11T02:47:42Zyfjiangyfjiang@suse.com
<p>The test create_hdd_gnome[0] has done the common installation automation for tumbleweed,<br>
while three cases consoletest_setup, hostname, and x11setup, are not included in [0].<br>
Specifically, the three cases are solid dependencies if the subsequent gnome testing needs<br>
to launch terminal or in-depth GNOME testing.</p>
<p>Therefore, at the moment, the three cases need to include in individual test cases before<br>
a real testing starts. e.g. [1]</p>
<p>The ticket targets to move cases of consoletest_setup, hostname, and x11setup from gnome<br>
tests (e.g. [1]) to create_hdd_gnome[0], and make a proper dependencies between relevant<br>
gnome tests and create_hdd_gnome.</p>
<p>We could focus on the tuning between [0] and [1] at the moment, and follow up by populating<br>
more gnome test cases depended on the refreshed create_hdd_gnome.</p>
<p>[0] <a href="https://openqa.opensuse.org/tests/688857" class="external">https://openqa.opensuse.org/tests/688857</a> <br>
[1] <a href="https://openqa.opensuse.org/tests/688970" class="external">https://openqa.opensuse.org/tests/688970</a></p>
openQA Tests - action #36871 (Resolved): [sle15sp1][desktop] Comprehensive CJK automation.https://progress.opensuse.org/issues/368712018-06-07T00:10:29Zyfjiangyfjiang@suse.com
<p>This is a tickets holder for automating the overall experiences for CJK users, including the following 3 areas:</p>
<ul>
<li>ibus input method, as well as the gnome-initial-setup (how SLE triggers the configuration)</li>
<li>key elements translation (overall installer UI when CJK is chosen as a major language, default major desktop items)</li>
<li>aesthetically correctness of CJK fonts in both CJK environment and English environment</li>
</ul>
<p>One of the languages in CJK can be used here to implement the concrete test case.</p>
openQA Tests - action #36694 (New): [sle15sp3][desktop] Implement test cases for gnome-software/g...https://progress.opensuse.org/issues/366942018-06-01T07:44:53Zyfjiangyfjiang@suse.com
<p>We have been lack of checking the packagekit mechanism in early development phase, and experienced some tough time to do a thorough check in the past.</p>
<p>Automating such a scenario on one hand will make sure the toolset is tested in early development, on the other hand, it will remind us update-test-* <br>
should be ready in early development phase.</p>
<p>Notice the update-test-* packages will be intended to remove in GMC. So the case is supposed to be failed (or softfailed) in GMC build.</p>
openQA Tests - action #36691 (Rejected): [sle12sp4][desktop] Implement test cases for gnome-packa...https://progress.opensuse.org/issues/366912018-06-01T07:42:45Zyfjiangyfjiang@suse.com
<p>We have been lack of checking the packagekit mechanism in early development phase, and experienced some tough time to do a thorough check in the past.</p>
<p>Automating such a scenario on one hand will make sure the toolset is tested in early development, on the other hand, it will remind us update-test-* <br>
should be ready in early development phase.</p>
<p>Notice the update-test-* packages will be intended to remove in GMC. So the case is supposed to be failed (or softfailed) in GMC build.</p>
openQA Tests - action #35272 (Resolved): [sle15][desktop] Make gnote_rename_title, gnote_undo_red...https://progress.opensuse.org/issues/352722018-04-20T07:39:29Zyfjiangyfjiang@suse.com
<p>As the parents ticket analyzed:</p>
<p><a href="https://progress.opensuse.org/issues/27169#note-11" class="external">https://progress.opensuse.org/issues/27169#note-11</a></p>
openQA Tests - action #34789 (New): [sle12sp4][desktop] Check license pop-up when ad-hoc licensed...https://progress.opensuse.org/issues/347892018-04-12T11:41:10Zyfjiangyfjiang@suse.com
<p>Regarding bsc#1089327 New: Nvidia license isn't displayed when selecting nvidia drivers in the installer</p>
<p>We need to check necessary licenses pop-up. In the context of SLE-12-SP4,<br>
the target packages list is:</p>
<ul>
<li>AdobeICCProfiles</li>
<li>agfa-fonts</li>
<li>ati-fglrxG01</li>
<li>ati-fglrxG01-KMP</li>
<li>ati-fglrxG02</li>
<li>ati-fglrxG02-KMP</li>
<li>banshee-1-samsung-codecs</li>
<li>cxgb3-firmware</li>
<li>cxgb4-firmware</li>
<li>fetchmsttfonts</li>
<li>gst-fluendo-mp3</li>
<li>gst-fluendo-plugins</li>
<li>gstreamer-0_10-fluendo-mp3</li>
<li>gstreamer-fluendo-mp3</li>
<li>ICAClient</li>
<li>IPAGothic</li>
<li>IPAMincho</li>
<li>IPAPGothic</li>
<li>IPAPMincho</li>
<li>IPAUIGothic</li>
<li>java-1_5_0-sun-alsa</li>
<li>java-1_5_0-sun-demo</li>
<li>java-1_5_0-sun-devel</li>
<li>java-1_5_0-sun</li>
<li>java-1_5_0-sun-jdbc</li>
<li>java-1_5_0-sun-plugin</li>
<li>java-1_5_0-sun-src</li>
<li>java-1_6_0-sun-alsa</li>
<li>java-1_6_0-sun-demo</li>
<li>java-1_6_0-sun-devel</li>
<li>java-1_6_0-sun</li>
<li>java-1_6_0-sun-jdbc</li>
<li>java-1_6_0-sun-plugin</li>
<li>java-1_6_0-sun-src</li>
<li>nvidia-gfx</li>
<li>nvidia-gfxG01</li>
<li>nvidia-gfxG01-KMP</li>
<li>nvidia-gfxG02</li>
<li>nvidia-gfxG02-KMP</li>
<li>nvidia-gfx-KMP</li>
<li>s390-tools-zdsfs</li>
<li>snipl</li>
<li>websphere-as_ce</li>
<li>x11-video-fglrxG01</li>
<li>x11-video-fglrxG02</li>
<li>x11-video-nvidia</li>
<li>x11-video-nvidiaG01</li>
<li>x11-video-nvidiaG02</li>
<li>xep</li>
<li>xep-license</li>
</ul>
<p>The test step is preferred to happen during installation (using<br>
yast installer)and after installation (using zypper).</p>
<p>Scenario 1.</p>
<p>During the installation, get into software detailed management.</p>
<ul>
<li>Step through the following actions </li>
<li>select one of the packages to install</li>
<li>go to next step to check the license pop-up</li>
<li>select another listed packages to install</li>
<li>go to next step ...</li>
<li>...</li>
<li>[until all packages in the list are covered]</li>
</ul>
<p>Scenario 2.</p>
<p>Boot to a installed system, install through each packages one by one,<br>
check each of the licenses is popped up.</p>
openQA Tests - action #34786 (In Progress): [sle15sp1][desktop] Check license pop-up when ad-hoc ...https://progress.opensuse.org/issues/347862018-04-12T11:29:22Zyfjiangyfjiang@suse.com
<p>Regarding bsc#1089329 Nvidia license isn't displayed when selecting nvidia drivers in the installer </p>
<p>We need to check necessary licenses pop-up. In the context of SLE-15,<br>
the Nvidia drivers package set (nvidia-gfx*) should be checked for this.</p>
<p>The test step is preferred to happen during the installation (using<br>
yast installer)and after installation (using zypper).</p>
<p><strong>Scenario 1.</strong> </p>
<p>During the installation, get into software detailed management.</p>
<p>Step through the following actions </p>
<ul>
<li>select a nvidia-gfx-* packages to install</li>
<li>go to next step to check the license pop-up</li>
<li>select another nvidia-gfx-* package to install</li>
<li>go to next step ...</li>
<li>...</li>
<li>[until all nvidia-gfx* packages are covered]</li>
</ul>
<p><strong>Scenario 2.</strong></p>
<p>Boot to a installed system, install through each nvidia-gfx* drivers one by one,<br>
check each of the license is popped up.</p>
openQA Tests - action #33781 (Resolved): [sle15sp1][desktop]Update test case firefox_developertool.https://progress.opensuse.org/issues/337812018-03-26T04:54:59Zyfjiangyfjiang@suse.com
<p>The firefox_developertool testing needles looks "too restrictive" to me.</p>
<p><a href="https://openqa.suse.de/tests/1564559#step/firefox_developertool/17" class="external">https://openqa.suse.de/tests/1564559#step/firefox_developertool/17</a></p>
<p>The page changes from time to time, we might not want to depend that DOM<br>
structure to define the case.</p>
<p>To update the test case:</p>
<ol>
<li>use a fixed while complicated html&css&js page to test</li>
<li>It should be better if we check each tab is there and switchable
"Inspector"
"Console"
"Debugger"
...</li>
</ol>
openQA Tests - action #33211 (Resolved): [sle15sp1][desktop] Better handling wayland and x11 test...https://progress.opensuse.org/issues/332112018-03-14T07:18:19Zyfjiangyfjiang@suse.com
<p>Currently the desktop test cases are organized as a bit scattered:</p>
<ul>
<li>Desktop Applications -> * (Wayland)</li>
<li>Functional -> extra_tests_on_gnome (X11)</li>
<li>Functional -> gnome (X11)</li>
<li>Functional -> we-module (Wayland)</li>
<li>Functional -> yast2_gui (X11)</li>
</ul>
<p>Maybe there are more to be revealed.</p>
<p>Basically wheather the test cases running on X11 or Wayland is currently<br>
based on how the system, upon which the test cases is running, was installed.</p>
<ul>
<li>For the installation adapted within the test case, it depends on the status of Workstation Extension and selected system role</li>
<li>For the test cases depending on the standalone installation case (e.g. create_hdd_*), it depends on whether the installation case has Workstation Extension and GNOME system role</li>
</ul>
<p>The goals can be phrased as:</p>
<ol>
<li>Have a more organized way to tell openQA result readers that the testing was running on Wayland or X11</li>
<li>Migrate all those X11 cases into Wayland, so that we could make sure the GUI test cases already automated should be run on Wayland</li>
</ol>
openQA Tests - action #33208 (Resolved): [sle15sp1][desktop] Integrating of fix for openQA firefo...https://progress.opensuse.org/issues/332082018-03-14T05:43:22Zyfjiangyfjiang@suse.com
<p>We had firefox needles and scripts rebasing in the past couple of days, while the subsequent cases do not yet work very well.</p>
<p>So I am opening this issue to track firefox scripting in Desktop Application group. Let's integrate everything here until the full solution is provided.</p>
<p>@chingkai,</p>
<p>I am putting it in you queue :-) Please feel free to split them into small tasks, if the failed reasons are too complicated to handle with quick fixes. Thank you!</p>
openQA Tests - action #25608 (Resolved): Update failure cases on updates_packagekit_gpkhttps://progress.opensuse.org/issues/256082017-09-27T10:41:54Zyfjiangyfjiang@suse.com
<p>The following cases has been failed in SLE-15 phase, because tty7 in sle-15 is a <br>
constant greeting tty in gnome 3.26, clicking "alt-f2' does not pop up command <br>
running dialog.</p>
<p><a href="https://openqa.suse.de/tests/1187904#step/updates_packagekit_gpk/8" class="external">https://openqa.suse.de/tests/1187904#step/updates_packagekit_gpk/8</a></p>
<p>Maybe things used in start_wayland_plasma5.pm (console('x11')->{args}->{tty} = 3)<br>
can be reused here to switch to the correct tty for continuing with the rest of <br>
testing.</p>
<p>This is urgent :-)</p>
openQA Project - action #13920 (Resolved): Showing context builds test result in the view of curr...https://progress.opensuse.org/issues/139202016-09-27T02:35:12Zyfjiangyfjiang@suse.com
<p>Hi,</p>
<p>This is a feature request.</p>
<p>When reviewing a specific set of test, there's a convenient tab showing <br>
all the previous results:</p>
<p><a href="http://openqa.suse.de/tests/579565#previous" class="external">http://openqa.suse.de/tests/579565#previous</a></p>
<p>However, it is not seldom we take a test review from the middle of all <br>
results where an issue happens. In that case, both previous and latter <br>
results of the current would make sense. (more like "grep -C" <br>
instead of "grep -A")</p>
<p>So making the tab's view showing the test status of the context builds <br>
will help.</p>