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

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

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

    # Anaconda hub
    assert_screen "anaconda_main_hub", 300; #

}

sub test_flags {
    # without anything - rollback to 'lastgood' snapshot if failed
    # 'fatal' - whole test suite is in danger if this fails
    # 'milestone' - after this test succeeds, update 'lastgood'
    # 'important' - if this fails, set the overall state to 'fail'
    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;`

			`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 an iscsi test, and a support_server test to support it Summary: this is following a SUSE model for tests where we need a server end but don't want setting up the server to constitute a real test in itself, we want it to be stable. The 'support_server' test just boots a pre-built (by createhdds) disk image, sets up networking, and runs the iSCSI server. To run the iSCSI test we need to handle networking config in anaconda (or we would need to set the support server up as a DHCP server, which may be worth considering), so this adds that. We also need to be able to specify the target device for a volume in custom partitioning, so this adds that too. Test Plan: Build the necessary support server disk image (use D883), then run the test and make sure it works. Also make sure all other tests continue to work. Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D884 2016-06-09 15:43:46 +00:00			`$self->select_disks(disks=>2);`
add multiple disks test 2015-03-05 12:57:47 +00:00			`assert_and_click "anaconda_spoke_done";`

			`# Anaconda hub`
			`assert_screen "anaconda_main_hub", 300; #`

			`}`

			`sub test_flags {`
			`# without anything - rollback to 'lastgood' snapshot if failed`
			`# 'fatal' - whole test suite is in danger if this fails`
			`# 'milestone' - after this test succeeds, update 'lastgood'`
			`# 'important' - if this fails, set the overall state to 'fail'`
			`return { fatal => 1 };`
			`}`

			`1;`

			`# vim: set sw=4 et:`