action #109211
Updated by szarate almost 2 years ago
## Observation This test is executing a lot of steps testing the UI, but causes failures which in this case, when the mouse was moved, the copy menu was selected (for some weird reason) Also the module is doing a full blown installation, when it could boot from HDD. Dee proposed that we could do features and functionalities of Wireshark via console, and verify that the app really can be started, from the GUI point of view... openQA test in scenario sle-15-SP4-Online-x86_64-we-module@64bit-2gbram fails in [wireshark](https://openqa.suse.de/tests/8429448/modules/wireshark/steps/17) I have checked ## Test suite description Maintainer: QE Core Execute WE-related tests on SLE15 installations with Vit, and his feeling is that it is ok to proceed with WE module enabled (for products earlier than SLE15, the change. scenarios are we, we-ftp, we-http). ## Reproducible Fails since (at least) Build [43.1](https://openqa.suse.de/tests/7262580) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit-2gbram&test=we-module&version=15-SP4)