Clocks: handle auth, check we actually launched the app

Clocks' aaa_setup did not ever actually check the app launched
properly. It also doesn't handle granting permissions if
necessary, which the apps_startstop test for Clocks does do.

This makes the permission check in the apps_startstop test more
efficient, and adds it to the Clocks app aaa_setup test too.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2022-06-30 13:56:29 -07:00
parent e13c716ab9
commit f81dab6739
2 changed files with 11 additions and 4 deletions

View File

@ -22,7 +22,13 @@ sub run {
# Start the Application
menu_launch_type("clocks");
wait_still_screen(2);
assert_screen ["apps_run_clocks", "apps_run_access"];
# give access rights if asked
if (match_has_tag 'apps_run_access') {
click_lastmatch;
assert_screen 'apps_run_clocks';
}
# Make it fill the entire window.
send_key("super-up");
wait_still_screen(2);

View File

@ -9,11 +9,12 @@ sub run {
my $self = shift;
# Start the application
start_with_launcher('apps_menu_clocks');
assert_screen ["apps_run_clocks", "apps_run_access"];
# give access rights if asked
if (check_screen('apps_run_access', 1)) {
assert_and_click 'apps_run_access';
if (match_has_tag 'apps_run_access') {
click_lastmatch;
assert_screen 'apps_run_clocks';
}
assert_screen 'apps_run_clocks';
# Register application
register_application("gnome-clocks");
# close the application