mirror of
https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git
synced 2024-09-09 01:57:22 +00:00
This comes from trying to fix the annoying recurring problem with mistypes in KDE which has been going on since at least December. First, we add the attempt to kind of 'precache' the kicker menu in aasetting.pm. Then, I thought, all this snapshot loading has to be putting a lot of load on the workers. And when each subtest passes, it shouldn't really be necessary - they all end with quit_with_shortcut(), which verifies that the app exited and we got back to a blank desktop, so successful subtests should not usually interfere with each other. We probably only want to rollback on *failed* subtests, which is in fact openQA's default behavior. There only seems to be one case where a test changes the system state such that later tests might be affected, so I kept always_rollback just for that one. I've run this through three cycles on GNOME and KDE and it looks good. Signed-off-by: Adam Williamson <awilliam@redhat.com>
40 lines
894 B
Perl
40 lines
894 B
Perl
use base "installedtest";
|
|
use strict;
|
|
use testapi;
|
|
use utils;
|
|
|
|
# This test checks that Kmouth starts.
|
|
|
|
sub run {
|
|
my $self = shift;
|
|
|
|
# Start the application
|
|
menu_launch_type 'kmouth';
|
|
sleep 2;
|
|
# Deal with the welcome screens
|
|
assert_screen ["kde_next", "kde_finish"], 90;
|
|
while (match_has_tag "kde_next") {
|
|
assert_and_click "kde_next";
|
|
sleep 2;
|
|
assert_screen ["kde_next", "kde_finish"];
|
|
}
|
|
# Settings close
|
|
assert_and_click 'kde_finish';
|
|
wait_still_screen 2;
|
|
# Check that it is started
|
|
# July 19th, I realized that kmouth test has been failing,
|
|
# but it seems that it takes more time to run than
|
|
# the needle is willing to wait. Adding wait time.
|
|
assert_screen('kmouth_runs', timeout => 300);
|
|
# Close the application
|
|
quit_with_shortcut();
|
|
}
|
|
|
|
sub test_flags {
|
|
return {};
|
|
}
|
|
|
|
1;
|
|
|
|
# vim: set sw=4 et:
|