After the review, when the requirements have been
added, the tests started to behave a little differently
and some fixes had to be added to make it pass with
no problems.
Also, this PR adds a function to change Gnome
default settings.
This adds a test for remote connection. It consists of a server part
in which Gnome RDP connection is set up, enabled, and the server is run,
and the client part that uses Connections as a client to connect to the
server.
The test is considered successful when the connection is established
and the user has logged into the system.
Fixes: https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/333
In a virtual machine, it takes a couple of seconds for the
upper panel to go away and show the terminal prompt.
Let's make it wait 60 seconds to be absolutely sure.
There's no 'go to 2' button any more, we'll just click a random
section (Windows) and check that. This would also work fine for
the old style if we still need that - just add the '2' button to
gte_shortcuts_one and make sure it's the click area.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This enables the unwanted_packages test we set up for Workstation
a while ago on KDE as well. They want to ensure gtk2 isn't on
KDE installs.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This PR adds a start-stop test for Kleopatra that will replace
the KGpg application. It does not, however, remove the KGpg
start-stop test from the suite, as the KGpg is not gone yet.
We will remove it in a separate commit when time has come.
Fixes: https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/405
Change the start command to kleopatra
Move needle to generic space
Remove checking the selection box
The test failed because one of the applications ceased to exist
on the installation media. The fix brings a different set of
applications and more to it - the applications get installed
during the test so we probably won't have to deal with similar
issue in the future. Or at least not that often.
Fixes: https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/412
timedatectl now refuses to set the date to before the date when
systemd was built, so let's just use date instead.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This makes us create a generic cloud disk image and then run
tests on it, just like we do for Workstation and KDE lives,
everything netinst, Silverblue, and a container image. This is
intended to help avoid anything like
https://bugzilla.redhat.com/show_bug.cgi?id=2390898 happening
again - if we'd had these tests set up and gating enabled, the
update that caused that bug would've been gated.
This requires some changes that affect other things: bind mounting
the whole of /dev in our mock config when using simple isolation,
and forcing START_AFTER_TEST to "" for kiwi_build (this is needed
to override the setting of it in the updates-cloud flavor). bind
mounting is what koji does for 'real' kiwi build jobs so it's fine
(in fact, better); previously the mock config was shared with
livemedia-creator, but we don't use that any more so it's not a
problem.
It's a bit icky when we get to the point of having *multiple*
+START_AFTER_TEST settings, but I can't see another way to get
everything right here and still share the test suite definition
with compose tests.
Moving the definition of KIWI_PROFILE for container tests is not
strictly related, but I noticed it was weird while working on
this and couldn't leave it alone.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
As reported by @yselkowitz , ftp is no longer in ELN, so this
test fails on ELN composes. autofs is in ELN, has minimal
dependencies and doesn't change often, so it looks like a good
option.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Test "TCP/IPv4 larger transfer, tap" is flaking currently, so
let's disable it. Paul has reproduced the issue and is working on
the fix so no further purpose is served by failing on it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The security fix has been removed for now; we're removing this
workaround so we'll notice if it gets broken again.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
we really don't need to, and the new design that's currently in
Workstation but not yet Silverblue makes it awkward. Just check
one page.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is intended for things like system monitor where there's
constant motion on the app screen so we can't wait_still_screen.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
If the test settings indicate not to create a local user account,
let's uncheck the relevant box. This should fix the KDE
install_no_user test.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
KDE needs a kde-settings update, but everything else should be
showing the new background now. Add a needle for it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We never get direct to installmethod any more, I'm pretty sure -
we always go through language selection. This may change if we
ever fix up the gnome-initial-setup stuff, but for now let's
simplify.
However, web UI now has a date/time page that shows on KDE but
apparently not on GNOME. So if we hit that, click through it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
GNOME Software with the dnf5 backend prompts for GPG key import
if it hasn't already happened. We need to handle that. Luckily
I don't think we can get both this *and* the 'download unsigned'
needle, so we just make them alternates.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We don't crash on the lock screen in Rawhide GNOME now, but my
fix isn't perfect - the pointer is somehow broken on the lock
screen, so we can't click anything. tab doesn't work either, so
we just can't switch user from the lock screen till this is
fixed better. So for GNOME on Rawhide, we'll skip switching from
the lock screen and just do another 'normal' switch.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This reverts commit 6b734bd9fa. It
seems the test still fails at a later stage due to issues with
the lock screen, even though I was sure it passed on staging. Gr.
When Software complains about something, it shows a grey banner
in the lower part with a button to click (Details).
The update test has not utilized this anyhow, so if it happened,
we would not know what the error was.
This fix makes sure to click on the Details button when it
appears, revealing the reason behind it, which could help
us understand what happened.
Thanks to @luap99 for the neat idea here. It's valuable to run
the upstream integration tests both rooted and rootless - some
of the tests are unique to each mode, and other tests may pass
in one but fail in the other. However, we don't want to double
the execution time of the test. We could duplicate the test and
have rooted/rootless versions, but that increases load.
This is a neat trick: instead, just run the tests with root on
x86_64 but rootless on other arches (which for now is just
aarch64). This way we should get pretty much full coverage with
the same test execution time and overall load as before.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Until https://github.com/bats-core/bats-core/pull/1114 we can't
easily filter out specific tests in a bats run. So let's hack it
up with a sed that just negates the behavior of --filter - we
don't need to use its default behavior. Then we can use --filter
to filter out specific tests, like this. Use it to filter out
the test that's known to fail with recent kernels.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Don't run only a minor subset of the tests instead run all of them. The
main advantage is that we get much better coverage and upstream don't
need to maintain an extra subset of tags. Of course tests will be much
slower now as it will now run like 11x the amount of test cases.
Fixes: https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/373
Signed-off-by: Paul Holzinger <pholzing@redhat.com>
rootless podman was broken on new installs because shadow-utils
was changed not to assign subuid/subgid ranges to new users by
default, because Security.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
New button were added to the Calculator's Basic view,
which allow access to constants and functions. In this test,
we check some of the constants and functions.
This has always incorrectly been a race, it looks like, but for
some reason we were winning it before but we're losing it now.
The client seems to be pinging while the server's still typing
stuff into grub. So let's have the server set a mutex, and the
client wait for it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Some of the buttons disappeared from the basic view of the applications.
This, for the times being, removes the operations that used these
buttons, for the application test to pass again.
All the old patterns we accept and differing files they might be
in are obsolete now, I'm pretty sure - I checked that in F41
tests we get the most recent messages and they're all in syslog.
So drop all of those. But we need to add new handling for dnf5,
now anaconda switched to that and the messages changed again.
I can't find any messages in the dnf5 logs that confirm the
correct URL was used, unfortunately - these are the best I can
find.
Also, since 31cd5e7 , we won't get the base repository error
strings we're looking for any more, even if there *is* a problem
with the base repo. I don't think there's any single error we
can rely on getting any more, so we'll have to trust that the
other checks are sufficient, or figure out ones to add as we go
along if not.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
