Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Select yast development pattern only #15693

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Expand Up @@ -28,7 +28,7 @@ schedule:
- installation/clock_and_timezone/accept_timezone_configuration
- installation/authentication/use_same_password_for_root
- installation/authentication/default_user_simple_pwd
- installation/select_patterns
- installation/select_visible_patterns_from_bottom
- installation/installation_settings/validate_default_target
- installation/bootloader_settings/disable_boot_menu_timeout
- installation/launch_installation
Expand Down
Expand Up @@ -24,7 +24,7 @@ schedule:
system_role:
- installation/system_role/accept_selected_role_SLES_with_GNOME
software:
- installation/select_patterns
- installation/select_visible_patterns_from_bottom
system_validation:
- console/validate_installed_packages
- console/validate_installed_patterns
Expand Down
Expand Up @@ -28,7 +28,7 @@ schedule:
- installation/clock_and_timezone/accept_timezone_configuration
- installation/authentication/use_same_password_for_root
- installation/authentication/default_user_simple_pwd
- installation/select_patterns
- installation/select_visible_patterns_from_bottom
- installation/installation_settings/validate_default_target
- installation/bootloader_settings/disable_boot_menu_timeout
- installation/launch_installation
Expand Down
Expand Up @@ -22,7 +22,7 @@ schedule:
- installation/clock_and_timezone/accept_timezone_configuration
- installation/authentication/use_same_password_for_root
- installation/authentication/default_user_simple_pwd
- installation/select_patterns
- installation/select_visible_patterns_from_bottom
- installation/installation_settings/validate_default_target
- installation/bootloader_settings/disable_boot_menu_timeout
- installation/launch_installation
Expand Down
Expand Up @@ -22,7 +22,7 @@ schedule:
- installation/clock_and_timezone/accept_timezone_configuration
- installation/authentication/use_same_password_for_root
- installation/authentication/default_user_simple_pwd
- installation/select_patterns
- installation/select_visible_patterns_from_bottom
- installation/installation_settings/validate_ssh_service_enabled
- installation/installation_settings/open_ssh_port
- installation/bootloader_settings/disable_boot_menu_timeout
Expand Down
30 changes: 30 additions & 0 deletions tests/installation/select_visible_patterns_from_bottom.pm
@@ -0,0 +1,30 @@
# SUSE's openQA tests
#
# Copyright 2022 SUSE LLC
# SPDX-License-Identifier: FSFAP

# Summary: Select a pattern from the bottom
# You can pass
# PATTERNS=yast-development
#
# Maintainer: QA SLE YaST team <qa-sle-yast@suse.de>

use base 'y2_installbase';
use strict;
use warnings;
use testapi;

sub run {
my ($self) = @_;
$self->go_to_patterns();
my @patterns = grep($_, split(/,/, get_required_var('PATTERNS')));
# delete special 'default' key from the check
@patterns = grep { $_ ne 'default' } @patterns;
Copy link
Contributor

@jknphy jknphy Oct 31, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't need this line, we should remove 'default' from settings via MR.

Copy link
Contributor

@JRivrain JRivrain Nov 2, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically yes, however someone checking the settings can interpret that "PATTERNS=yast_develpoment" may mean only yast development, and not default patterns, as all other tests using that variable specify it otherwise.

Copy link
Contributor

@jknphy jknphy Nov 2, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

our way is to check the name of the test module, if we pass as settings or test data is just by our own convenience, we have tests/installation/select_only_visible_patterns_from_top.pm for disambiguation with only in the name.

# specific for yast development at the end of list
wait_screen_change { send_key 'alt-end'; }
save_screenshot;
$self->select_visible_unselected_patterns([@patterns]);
$self->accept_changes();
}

1;