openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-04-01T07:57:57ZopenSUSE Project Management Tool
Redmine QA - action #109358 (Resolved): [qe-core] Describe desktop maintenance testinghttps://progress.opensuse.org/issues/1093582022-04-01T07:57:57Zyfjiangyfjiang@suse.com
<p>Current QE LSG setup mixed the legacy product and maintenance QA as functional squads. While it is not the case for desktop related testing yet, it may be a good idea to think about the possibility of getting the desktop testing closer to the current QE map. To move this a bit forward, currently I am looking into what knowledge and workload are needed for the desktop maintenance testing, but I have little knowledge about maintenance related testing. So knowing more about the general maintenance tasks, taking desktop as an example, could be a good start. There are some information I am thinking about to gather:</p>
<pre><code> - what is the current process to review the distributed tasks in desktop maintenance testing area?
- what is the current process to execute/implement the testing tasks in desktop maintenance testing area?
- what is the expected KPI, timing of finishing/scope of the relevant workload?
- where (ie. with which toolchains) can people proceed concrete working items, tasks and workload in desktop maintenance testing area?
</code></pre>
<p>If there is anything more we should share about the topic, please do not hesitate to add. Thanks!</p>
<p>To provide more context there's <a href="https://confluence.suse.com/display/qasle/Tests+Maintained+by+QE+Core?focusedCommentId=729809203#comment-729809203" class="external">this</a> comment on QE Core's list of mantained tests and #93351</p>
openQA Tests - action #89975 (Resolved): [desktop][sle15sp3] Test the "secure boot + dual boot" f...https://progress.opensuse.org/issues/899752021-03-12T08:26:13Zyfjiangyfjiang@suse.com
<p>SLE release team noticed a necessity of adapting a TW openqa test for our SLE product:<br>
<a href="https://openqa.opensuse.org/tests/1657341#step/boot_windows/2" class="external">https://openqa.opensuse.org/tests/1657341#step/boot_windows/2</a><br>
to cover the "secure boot + dual boot" for SLED</p>
<p>The case contributed to found a bug on TW, and SLE-15-SP3 is also affected by<br>
the problem:</p>
<p><a href="https://bugzilla.suse.com/show_bug.cgi?id=1183073" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1183073</a></p>
<p>Please let us have the same test on SLE so we can be sure this can be tested for future releases.</p>
openQA Tests - action #56624 (New): [desktop][tw] Implement remote desktop cases on Tumbleweed fo...https://progress.opensuse.org/issues/566242019-09-09T09:05:08Zyfjiangyfjiang@suse.com
<p>We have cases for the coverage of xvnc/tigervnc, and it would be a good thing<br>
to migrate them to Tumbleweed. The related cases are:</p>
<ul>
<li>onetime_vncsession_xvnc_tigervnc.pm</li>
<li>onetime_vncsession_xvnc_remmina.pm</li>
<li>onetime_vncsession_multilogin_failed.pm</li>
</ul>
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 #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 #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 #35452 (Resolved): [sle][functional][y][easy] Adapt EULA translation check ...https://progress.opensuse.org/issues/354522018-04-25T01:05:16Zyfjiangyfjiang@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>From earlier talks with Oliver, it makes sense to allow openQA to check the EULA translation<br>
in the beginning of installation, appending to the test cases accept_license.pm. Both GUI<br>
and Text based installers are considered here:</p>
<p><a href="http://openqa.suse.de/tests/1641951#step/accept_license/1" class="external">http://openqa.suse.de/tests/1641951#step/accept_license/1</a><br>
<a href="http://openqa.suse.de/tests/1641912#step/accept_license/1" class="external">http://openqa.suse.de/tests/1641912#step/accept_license/1</a></p>
<p>Frederic also mentioned the translation is available in later release phase, e.g. probably the<br>
EULA translation will not be available until SLE-15-SP0 GMC.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> At least one other language than english is checked for in at least one scenario for both SLE15 and SLE12</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Switch the language pull down menu for EULA translation to a different language, e.g. Russian, check screen with needle, change language back and continue test for some other tests later</li>
<li>Select a proper test scenario where this should be executed</li>
</ul>
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>