It's not just Installation Destination, on aarch64 at least we
have lots of tests failing because entering the source or software
selection spokes didn't work. Let's try extra clicks for these
too.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The others have all been rebased to F41, so we had to bump the
Platform version to 41, but since Cheese is kinda dead these
days, its flatpak hasn't been bumped, and that makes building
the F39 ostree installer image fail. To work around this, sed
it out of the pungi config.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We do a menu_launch_type for kwalletmanager, so we'd better keep
a doublek workaround before that :/
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Also be a bit more consistent about asserting we saw a terminal
and waiting a bit before typing stuff. We can drop the doublek
workarounds from the keyring tests as we no longer use the
kicker to launch the terminal on KDE (we use ctrl-alt-t shortcut).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This started out as just factoring out the repeated pattern for
launching a terminal on the desktop that came in with the i3
tests. But as I worked on desktop_login, which is a major user
of it, I noticed some potential cleanups and improvements in the
user switching stuff, and also realized we can turn that test
back on for KDE now - user switching was re-enabled in KDE a year
ago and is advertised to be reliable.
I don't think the "switch user from a lock screen" test fully
worked before, as we did not verify that we'd really switched
back to an existing session rather than starting a new one. Now
we do. Using the terminal to verify the logged-in user on all
desktops just keeps things simpler than using the kicker menu
on KDE (though if typing proves unreliable on KDE I may switch
this back).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We seem to be having quite a few failures lately because the
viewer window in KDE never got maximized. This makes us a bit
more conservative at startup and puts the maximization / sentence
check in a send_key_until_needlematch loop to give it more
chances.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This avoids some magic waits by asserting screens (which is much
more reliable), and combines KDE and GNOME flows in the
passwordless test by adding some needle tags to the nautilus
needles.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Over the time, we have changed the test scripts so that the code
in the i3.pm library was no more needed. The only leftover was the
user config subroutine that could be moved to the only file that was
using it and we could get rid of the library file.
There are several other tests doing the same thing (but not as
safely, in some cases). To improve reliability and reduce
duplication, let's factor this out into utils.pm and reuse it
where appropriate.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
New anaconda-webui changes the disk selection flow a bit, this
adapts to it. We can drop the conditional and make it a straight
assert-and-click once the new webui is stable for F41 and F42.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is often failing on KDE on Rawhide ATM, apparently because
of a performance regression with software rendering. So let's
wait longer for the browser, but soft fail if it takes longer
than 45 seconds.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The behavior after we click 'Restart to Install Updates Now'
button has changed in KDE 6.2. The default choice is no longer
'Install Updates and Restart' (even though that's what the button
says), and there is no timer. So if we don't click anything, the
confirm overlay just stays open forever.
This makes us click on the appropriate confirmation button if we
see it. We can also use this to make the test run a bit faster on
other releases, I guess.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
In a couple of cases we type something that *doesn't* start with
a 'k', so we should use that other letter for the workaround.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This should make the installer image build test work for ELN,
so we can try doing some update tests on ELN.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
There's some ambiguity about the case of the ELN version string.
Currently it's "ELN", it's going to be "eln" soon. Let's just
always use case-insensitive comparisons.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
kernel.org is currently unreachable by IPv4 so this keeps failing.
Will re-enable when the site is fixed.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is now required (config.xml is gone), and Koji has been
doing it for a while. Koji uses a modified file it writes before
calling kiwi-ng, but we just use the stock one here.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We disabled the g-i-s live mode on Rawhide for now (as it was
getting too hard to maintain the patch downstream), so this test
should not expect it any more.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Let's not trust hitting enter in just one place but hit the save
button like we do elsewhere (this avoids an awkward issue where
hitting enter doesn't work on the new nautilus version). Also,
let's consolidate the needles under a sensible tag name.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We're dropping the live user mode patch from g-i-s downstream
because it's just too hard to maintain, apparently. So on Rawhide
the live image will boot to the welcome screen as normal, but
running the installer will give you newui rather than webui. If
you need a language other than English you have to sort it out
at the desktop before running the installer.
On first boot, g-i-s will show *all* screens, not skipping
language, keyboard layout or timezone, because we did not see
those in the installer.
This adapts the tests to handle the new flow, and should still
work with the other flows.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We disable it later in this test when repo_setup gets called, but
if stuff from it was installed by this `dnf -y update` call, that
can cause dep issues.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
