srbala/os-autoinst-distri-fedora
1
0
Fork 0
mirror of https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git synced 2024-11-14 10:44:22 +00:00
Code Issues Releases Activity
8e43dfa304
os-autoinst-distri-fedora/tests/disk_guided_empty.pm

46 lines
1.3 KiB
Perl
Raw Normal View History

add comments and documentation Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D481
2015-08-05 06:23:59 +00:00
use base "anacondatest";
Added 'server_simple' testsuite
2015-01-26 14:58:07 +00:00
use strict;
use testapi;
Move all remaining utility functions into exporter modules Summary: This adds a couple of new exporter modules, renames main_common to utils (this is a better name: openSUSE's main_common is functions used in main.pm, utils is what they call their module full of miscellaneous commonly-used functions), and moves a bunch of utility functions that were previously needlessly implemented as instance methods in base classes into the exporter modules. That means we can get rid of all the annoying $self-> syntax for calling them. We get rid of `fedorabase` entirely, as it's no longer useful for anything. Other base classes keep the 'standard' methods (like `post_fail_hook`) and methods which actually need to be methods (like `root_console`, whose behaviour is different in anacondatest and installedtest). Test Plan: Do a full test suite run and check everything lines up. There should be no functional differences from before at all, this is just a re-org. Reviewers: jskladan, garretraziel_but_actually_jsedlak_who_uses_stupid_nicknames Reviewed By: garretraziel_but_actually_jsedlak_who_uses_stupid_nicknames Subscribers: tflink Differential Revision: https://phab.qa.fedoraproject.org/D1080
2017-01-18 07:15:44 +00:00
use anaconda;
Add new testcases and methods for release identification.
2019-05-16 13:01:52 +00:00
use utils;
Added 'server_simple' testsuite
2015-01-26 14:58:07 +00:00
sub run {
revise storage: better test loading, shared disk selection Summary: This contains several tweaks to storage handling. It adds a method for disk selection which all the storage tests can share. It sets up a more extensible approach for main.pm to run the storage tests, instead of an ever-growing forest of 'else' clauses. Finally it sets up a couple of methods for changing partitioning schemes on the custom part screen and uses one of them in the software RAID test; the other will be used for other custom storage tests. This kills the two_disks needle. I could keep it and work it into select_disks, but it doesn't fit naturally and I really just don't see the point of the needle. The only thing we lose is we don't check that anaconda actually sees two disks in the 'attach two disks, only install to one' test (that's server_sata_multi), but the other multi-disk tests will serve to catch that case failing for some reason. What I actually intended to do was add some more tests for different custom part storage types, but it seemed a good idea to do some of this cleanup so that can be implemented efficiently. I'll have followups for that. Test Plan: Run all tests and ensure they work exactly as before (not just that they still pass, but that the correct test steps are actually scheduled in each case.) Reviewers: garretraziel, jskladan Reviewed By: garretraziel, jskladan Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D475
2015-07-31 08:31:27 +00:00
my $self = shift;
Add new testcases and methods for release identification.
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');
Added 'server_simple' testsuite
2015-01-26 14:58:07 +00:00
# Anaconda hub
revise storage: better test loading, shared disk selection Summary: This contains several tweaks to storage handling. It adds a method for disk selection which all the storage tests can share. It sets up a more extensible approach for main.pm to run the storage tests, instead of an ever-growing forest of 'else' clauses. Finally it sets up a couple of methods for changing partitioning schemes on the custom part screen and uses one of them in the software RAID test; the other will be used for other custom storage tests. This kills the two_disks needle. I could keep it and work it into select_disks, but it doesn't fit naturally and I really just don't see the point of the needle. The only thing we lose is we don't check that anaconda actually sees two disks in the 'attach two disks, only install to one' test (that's server_sata_multi), but the other multi-disk tests will serve to catch that case failing for some reason. What I actually intended to do was add some more tests for different custom part storage types, but it seemed a good idea to do some of this cleanup so that can be implemented efficiently. I'll have followups for that. Test Plan: Run all tests and ensure they work exactly as before (not just that they still pass, but that the correct test steps are actually scheduled in each case.) Reviewers: garretraziel, jskladan Reviewed By: garretraziel, jskladan Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D475
2015-07-31 08:31:27 +00:00
# Go to INSTALLATION DESTINATION and ensure one disk is selected.
Move all remaining utility functions into exporter modules Summary: This adds a couple of new exporter modules, renames main_common to utils (this is a better name: openSUSE's main_common is functions used in main.pm, utils is what they call their module full of miscellaneous commonly-used functions), and moves a bunch of utility functions that were previously needlessly implemented as instance methods in base classes into the exporter modules. That means we can get rid of all the annoying $self-> syntax for calling them. We get rid of `fedorabase` entirely, as it's no longer useful for anything. Other base classes keep the 'standard' methods (like `post_fail_hook`) and methods which actually need to be methods (like `root_console`, whose behaviour is different in anacondatest and installedtest). Test Plan: Do a full test suite run and check everything lines up. There should be no functional differences from before at all, this is just a re-org. Reviewers: jskladan, garretraziel_but_actually_jsedlak_who_uses_stupid_nicknames Reviewed By: garretraziel_but_actually_jsedlak_who_uses_stupid_nicknames Subscribers: tflink Differential Revision: https://phab.qa.fedoraproject.org/D1080
2017-01-18 07:15:44 +00:00
select_disks();
Added few more tests
2015-01-27 12:35:27 +00:00
revise storage: better test loading, shared disk selection Summary: This contains several tweaks to storage handling. It adds a method for disk selection which all the storage tests can share. It sets up a more extensible approach for main.pm to run the storage tests, instead of an ever-growing forest of 'else' clauses. Finally it sets up a couple of methods for changing partitioning schemes on the custom part screen and uses one of them in the software RAID test; the other will be used for other custom storage tests. This kills the two_disks needle. I could keep it and work it into select_disks, but it doesn't fit naturally and I really just don't see the point of the needle. The only thing we lose is we don't check that anaconda actually sees two disks in the 'attach two disks, only install to one' test (that's server_sata_multi), but the other multi-disk tests will serve to catch that case failing for some reason. What I actually intended to do was add some more tests for different custom part storage types, but it seemed a good idea to do some of this cleanup so that can be implemented efficiently. I'll have followups for that. Test Plan: Run all tests and ensure they work exactly as before (not just that they still pass, but that the correct test steps are actually scheduled in each case.) Reviewers: garretraziel, jskladan Reviewed By: garretraziel, jskladan Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D475
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')){
revise updates.img test to work with new anaconda (T759) Summary: per details in T759, the 'unipony' updates image we use to test the updates image features doesn't work with latest anaconda (f24 and Rawhide). I've built a new updates image which uses a neat anaconda feature that allows you to override CSS with a file in a special location; it sets the background for disk capacity texts on the INSTALLATION DESTINATION spoke to be pink. This lets us use a simple needle that just looks for a pink blob on that spoke, on the basis that it's unlikely there'll ever be a pink blob there for any other reason, so if there is one, the updates image worked. There will be an accompanying tools diff to change the updates disk image to use the new updates image. Test Plan: Do a test run and check the updates image tests pass and no other tests are broken. You'll need to pull in the tools diff and re-generate the updates disk image to check that test, the scsi_updates_img test should work with just this diff. Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D799
2016-04-01 15:00:47 +00:00
assert_screen "anaconda_install_destination_updates", 30;
Added few more tests
2015-01-27 12:35:27 +00:00
}
Add new testcases and methods for release identification.
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") {
Don't check version or pre-release note on banners This reduces the coverage of the identification test a bit but also *substantially* simplifies it. We run into a ton of problems when we try to check the version and prerelease text on screens where it appears on banners: * The banners differ between variants * The pre-release text is translated * The banners have gradients so for RTL languages, even if some text is untranslated (e.g. 'Fedora 31') it appears on a different background color than on LTR languages * The prerelease text is dark red; if it appears on a dark blue area of the banner this can trigger an os-autoinst needle comparison bug: https://progress.opensuse.org/issues/56822 All of this together means we wind up continually fighting these checks and we have a whole forest of needles just for them, and it doesn't seem worthwhile. So let's drop all the places where we were checking version and prerelease on banners, and only check them in two places where they appear on a grey background, which avoids most of the problems (we just need one version needle per release, and one prerelease needle per language). Signed-off-by: Adam Williamson <awilliam@redhat.com>
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)
Add new testcases and methods for release identification.
2019-05-16 13:01:52 +00:00
}
Added few more tests
2015-01-27 12:35:27 +00:00
Added 'server_simple' testsuite
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 {
corrected test_flags for tests
2015-01-28 12:42:34 +00:00
return { fatal => 1 };
Added 'server_simple' testsuite
2015-01-26 14:58:07 +00:00
}
1;
# vim: set sw=4 et:
Reference in New Issue Copy Permalink