2015-08-05 06:23:59 +00:00
|
|
|
use base "installedtest";
|
2015-05-13 11:00:46 +00:00
|
|
|
use strict;
|
|
|
|
|
use testapi;
|
|
|
|
|
|
2015-07-17 10:52:56 +00:00
|
|
|
|
2015-05-13 11:00:46 +00:00
|
|
|
sub run {
|
2015-07-15 05:00:47 +00:00
|
|
|
my $self = shift;
|
2015-08-06 09:01:41 +00:00
|
|
|
my $password = get_var("USER_PASSWORD", "weakpassword");
|
2015-07-15 05:00:47 +00:00
|
|
|
|
2015-08-05 06:23:59 +00:00
|
|
|
# wait for GDM to appear
|
2015-07-17 10:52:56 +00:00
|
|
|
$self->boot_to_login_screen("graphical_login", 20);
|
2015-05-13 11:00:46 +00:00
|
|
|
|
2015-08-05 06:23:59 +00:00
|
|
|
# login as normal user
|
2015-05-13 11:00:46 +00:00
|
|
|
send_key "ret";
|
2015-07-17 10:52:56 +00:00
|
|
|
assert_screen "graphical_login_input";
|
|
|
|
|
type_string $password;
|
2015-05-13 11:00:46 +00:00
|
|
|
send_key "ret";
|
2015-08-05 06:23:59 +00:00
|
|
|
# wait until desktop appears
|
2015-07-17 10:52:56 +00:00
|
|
|
assert_screen "graphical_desktop_clean", 30;
|
convert upgrade tests to dnf-plugin-system-upgrade
Summary:
This is a first cut which more or less works for now. Issues:
1) We're not really testing the BUILD, here. All the test does
is try and upgrade to the specified VERSION - so it'll be using
the latest 'stable' for the given VERSION at the time the test
runs. This isn't really that terrible, but especially for TC/RC
validation, we might want to make things a bit more elaborate
and set up the repo for the actual BUILD (and disable the main
repos).
2) We'd actually need --nogpgcheck for non-Rawhide, at one
specific point in the release cycle - after Branching but
before Bodhi activation (which is when we can be sure all
packages are signed). This won't matter until 24 branches, and
maybe releng will have it fixed by then...if not, I'll tweak
it.
3) We don't really test that the upgrade actually *happened*
for desktop, at the moment - the only thing in the old test
that really checked that was where we checked for the fedup
boot menu entry, but that has no analog in dnf. What we should
probably do is check that GUI login works, then switch to a
console and check /etc/fedora-release just as the minimal test
does.
Test Plan:
Run the tests. Note that creating the desktop disk
image doesn't work ATM, so I can't verify the desktop test
works, but the minimal one seems to (with D565). There'll be
a matching diff for openqa_fedora_tools to update the test
case names there.
Reviewers: jskladan, garretraziel
Reviewed By: jskladan, garretraziel
Subscribers: tflink
Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D567
2015-09-10 21:49:13 +00:00
|
|
|
# check an upgrade actually happened (and we can log into a console)
|
|
|
|
|
$self->root_console(tty=>3);
|
2015-10-17 06:38:09 +00:00
|
|
|
$self->check_release(lc(get_var('VERSION')));
|
2015-05-13 11:00:46 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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:
|
