2015-08-05 06:23:59 +00:00
|
|
|
use base "anacondatest";
|
2015-01-26 14:58:07 +00:00
|
|
|
use strict;
|
|
|
|
|
use testapi;
|
2017-01-18 07:15:44 +00:00
|
|
|
use anaconda;
|
2019-05-16 13:01:52 +00:00
|
|
|
use utils;
|
2015-01-26 14:58:07 +00:00
|
|
|
|
|
|
|
|
sub run {
|
2015-07-31 08:31:27 +00:00
|
|
|
my $self = shift;
|
2019-05-16 13:01:52 +00:00
|
|
|
# If we want to test graphics during installation, we need to
|
|
|
|
|
# call the test suite with an "IDENTIFICATION=true" variable.
|
|
|
|
|
my $identification = get_var('IDENTIFICATION');
|
2015-01-26 14:58:07 +00:00
|
|
|
# Anaconda hub
|
2015-07-31 08:31:27 +00:00
|
|
|
# Go to INSTALLATION DESTINATION and ensure one disk is selected.
|
2017-01-18 07:15:44 +00:00
|
|
|
select_disks();
|
2015-01-27 12:35:27 +00:00
|
|
|
|
2015-07-31 08:31:27 +00:00
|
|
|
# updates.img tests work by changing the appearance of the INSTALLATION
|
|
|
|
|
# DESTINATION screen, so check that if needed.
|
rename BOOT_UPDATES_IMG_URL to TEST_UPDATES, add GRUBADD
Summary:
BOOT_UPDATES_IMG_URL is a pretty misleading name - it used to
be the actual URL, but now it's simply a boolean that decides
whether we look for the effect of the openQA updates image or
not. TEST_UPDATES seems clearer.
GRUBADD does the same thing as GRUB, on top of it. The point of
this is so we can add an option to the scheduler CLI that lets
you say 'run the normal tests, but with this updates image' -
so we can easily (albeit manually triggered) check the impact
of some anaconda change that needs testing. It should never be
set in the templates or the tests, it's there strictly for the
scheduler (whether that's fedora_openqa_schedule or literally a
person calling `client isos post`) to use as a kind of override.
The tests that test updates image loading will probably fail
when doing this, but all other tests should work as intended,
including ones that specify GRUB, becase the extra params will
just get added on top. That's why I invented a new var instead
of just letting the scheduler override GRUB's value when POST
ing.
Test Plan:
Check the rename didn't break anything (updates tests
still work). Run tests with GRUBADD param, make sure value is
correctly appended to cmdline both when GRUB is also specified
and when it is not.
Reviewers: jskladan, garretraziel
Reviewed By: garretraziel
Subscribers: tflink
Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D801
2016-04-08 20:21:29 +00:00
|
|
|
if (get_var('TEST_UPDATES')){
|
2016-04-01 15:00:47 +00:00
|
|
|
assert_screen "anaconda_install_destination_updates", 30;
|
2015-01-27 12:35:27 +00:00
|
|
|
}
|
2019-05-16 13:01:52 +00:00
|
|
|
# Here the self identification test code is placed.
|
|
|
|
|
my $branched = get_var('VERSION');
|
|
|
|
|
if ($identification eq 'true' or $branched ne "Rawhide") {
|
2019-10-16 18:08:24 +00:00
|
|
|
check_top_bar(); # See utils.pm
|
|
|
|
|
# we don't check version or pre-release because here those
|
|
|
|
|
# texts appear on the banner which makes the needling
|
|
|
|
|
# complex and fragile (banner is different between variants,
|
|
|
|
|
# and has a gradient so for RTL languages the background color
|
|
|
|
|
# differs; pre-release text is also translated)
|
2019-05-16 13:01:52 +00:00
|
|
|
}
|
2015-01-27 12:35:27 +00:00
|
|
|
|
2015-01-26 14:58:07 +00:00
|
|
|
assert_and_click "anaconda_spoke_done";
|
|
|
|
|
|
|
|
|
|
# Anaconda hub
|
|
|
|
|
assert_screen "anaconda_main_hub", 300; #
|
|
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
sub test_flags {
|
2015-01-28 12:42:34 +00:00
|
|
|
return { fatal => 1 };
|
2015-01-26 14:58:07 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
1;
|
|
|
|
|
|
|
|
|
|
# vim: set sw=4 et:
|
