os-autoinst-distri-rocky/needles/kde/desktop_package_tool_update_done.json

{
    "area": [
        {
            "height": 24,
            "type": "match",
            "width": 21,
            "xpos": 644,
            "ypos": 675
        }
    ],
    "properties": [],
    "tags": [
        "DESKTOP-kde",
        "desktop_package_tool_update_done"
    ]
}
add a desktop_update_graphical test Summary: Very similar to the CLI update test, but using the desktops' update applications. This is based off the CLI update test branch as it uses the shared functions that branch introduced. We do not use the fake update packages, as they don't really do anything useful for these tests; for dnf they can help us distinguish between issues with the dnf mechanism and issues with the repos, but we can't really tell that in the graphical case. So we only use the python3-kickstart package here. Test Plan: Run the test on both KDE and GNOME and ensure it performs as intended. I've been testing it on staging, so you can see it there. Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D1010 2016-09-20 22:32:44 +00:00			`{`
handle auth request for unsigned updates on KDE When a package is unsigned, KDE will prompt for authentication. Let's handle this. But count it as a soft fail, because puiterwijk claims that Rawhide packages will be autosigned from next week, so this should not happen and would indicate an unsigned package in the repos. We make the KDE 'update complete' needle area smaller because the wider area includes some transparency and so will only match if the update applet is open; this area will match whether it's open (no auth case) or not open (auth case - the applet seems to disappear after you provide the password in the auth prompt). Pushing without review as the test is in production so I want to make sure it works correctly. (Also, hey, check out that array match for assert_screen and that match_has_tag! This is gonna make some things so much easier...thanks upstream) 2016-09-24 00:21:54 +00:00			`"area": [`
			`{`
			`"height": 24,`
			`"type": "match",`
			`"width": 21,`
			`"xpos": 644,`
			`"ypos": 675`
			`}`
			`],`
			`"properties": [],`
			`"tags": [`
			`"DESKTOP-kde",`
			`"desktop_package_tool_update_done"`
			`]`
add a desktop_update_graphical test Summary: Very similar to the CLI update test, but using the desktops' update applications. This is based off the CLI update test branch as it uses the shared functions that branch introduced. We do not use the fake update packages, as they don't really do anything useful for these tests; for dnf they can help us distinguish between issues with the dnf mechanism and issues with the repos, but we can't really tell that in the graphical case. So we only use the python3-kickstart package here. Test Plan: Run the test on both KDE and GNOME and ensure it performs as intended. I've been testing it on staging, so you can see it there. Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D1010 2016-09-20 22:32:44 +00:00			`}`