os-autoinst-distri-fedora/tests/disk_guided_multi_empty_all.pm

use base "anacondatest";
use strict;
use testapi;
use anaconda;

sub run {
    my $self = shift;
    # Anaconda hub
    # Go to INSTALLATION DESTINATION and select two disks.
    select_disks(disks => 2);
    assert_and_click "anaconda_spoke_done";

    # Anaconda hub
    assert_screen "anaconda_main_hub", 300;

}

sub test_flags {
    return {fatal => 1};
}

1;

# vim: set sw=4 et:
add comments and documentation Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D481 2015-08-05 06:23:59 +00:00			`use base "anacondatest";`
add multiple disks test 2015-03-05 12:57:47 +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 multiple disks test 2015-03-05 12:57:47 +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 multiple disks test 2015-03-05 12:57:47 +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 select two disks.`
Add a perltidy check and apply it to the entire codebase Signed-off-by: Adam Williamson <awilliam@redhat.com> 2022-07-28 20:32:57 +00:00			`select_disks(disks => 2);`
add multiple disks test 2015-03-05 12:57:47 +00:00			`assert_and_click "anaconda_spoke_done";`

			`# Anaconda hub`
Add a perltidy check and apply it to the entire codebase Signed-off-by: Adam Williamson <awilliam@redhat.com> 2022-07-28 20:32:57 +00:00			`assert_screen "anaconda_main_hub", 300;`
add multiple disks test 2015-03-05 12:57:47 +00:00
			`}`

			`sub test_flags {`
Add a perltidy check and apply it to the entire codebase Signed-off-by: Adam Williamson <awilliam@redhat.com> 2022-07-28 20:32:57 +00:00			`return {fatal => 1};`
add multiple disks test 2015-03-05 12:57:47 +00:00			`}`

			`1;`

			`# vim: set sw=4 et:`