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

use base "installedtest";
use strict;
use testapi;
use utils;

sub run {
    my $self = shift;
    # for update testing, ensure the update repos are set up
    repo_setup if (get_var("ADVISORY_OR_TASK"));
}

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

1;

# vim: set sw=4 et:
Don't snapshot after wait_login tests (usually) We currently snapshot after every run of _console_wait_login or _graphical_wait_login, which means we snapshot twice on most update tests as those modules get run twice. However, we almost never use those snapshots. Snapshotting takes quite some time, and hits the disk pretty hard, so we should avoid it unless it is really needed. We only have a few modules that are not fatal (and so might use the snapshots), and most of those don't run after one of these tests, or run after a later module that's also a milestone. Best I can tell, only two test suites really need to use a snapshot from a login test: server_cockpit_updates and modularity_tests. To handle these and potential future cases, we'll add a new module that does nothing, but is marked 'milestone', so it will take a snapshot, and load that test after the login test if the var LOGIN_SNAPSHOT is set, and set that var for those two suites. Signed-off-by: Adam Williamson <awilliam@redhat.com> 2022-12-07 23:24:02 +00:00			`use base "installedtest";`
			`use strict;`
			`use testapi;`
			`use utils;`

			`sub run {`
			`my $self = shift;`
Ensure repos are set up for cockpit tests When running these tests on updates we inherit the main disk image from server_cockpit_default, which has the repo config, but the actual repo data is on HDD_3 which is not inherited. We need to re-download the updates here to ensure they're available to the tests (the automatic update test installs the dnf-automatic package, so it should pull it from the update repo if it is part of the update being tested). Signed-off-by: Adam Williamson <awilliam@redhat.com> 2024-04-25 23:52:09 +00:00			`# for update testing, ensure the update repos are set up`
			`repo_setup if (get_var("ADVISORY_OR_TASK"));`
Don't snapshot after wait_login tests (usually) We currently snapshot after every run of _console_wait_login or _graphical_wait_login, which means we snapshot twice on most update tests as those modules get run twice. However, we almost never use those snapshots. Snapshotting takes quite some time, and hits the disk pretty hard, so we should avoid it unless it is really needed. We only have a few modules that are not fatal (and so might use the snapshots), and most of those don't run after one of these tests, or run after a later module that's also a milestone. Best I can tell, only two test suites really need to use a snapshot from a login test: server_cockpit_updates and modularity_tests. To handle these and potential future cases, we'll add a new module that does nothing, but is marked 'milestone', so it will take a snapshot, and load that test after the login test if the var LOGIN_SNAPSHOT is set, and set that var for those two suites. Signed-off-by: Adam Williamson <awilliam@redhat.com> 2022-12-07 23:24:02 +00:00			`}`

			`sub test_flags {`
			`return {fatal => 1, milestone => 1};`
			`}`

			`1;`

			`# vim: set sw=4 et:`