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... view, as she's familiar with the tool from previous jobs. I have checked with Vit, Ideally, specially for a Network Admin, DevOps or CyberSec/DevSecOps, we could test the core functionalities of it via console, and his feeling is only verify that it the app really can be started, from the GUI point of view... and do all the extensive testing, on the console level ## AC 0. Test plan is ok documented on this ticket 1. GUI Testing of Wireshark is now reduced to proceed with a very basic test case 2. Equivalent testing as the change. GUI one is now done in the console per Dee's plan.