Univention Bugzilla – Bug 42587
Test App Center functionality: Dependency failures
Last modified: 2023-03-25 06:41:32 CET
We need tests to test the current behaviour in the following scenarios: - Test if an installation with a missing dependency fails - Test if an upgrade with a missing dependency fails - Test if the (dry) installation of an app that breaks another installed app fails - Test if the (dry) installation of an app that conflicts with another installed app fails +++ This bug was initially created as a clone of Bug #42580 +++ We need tests that verify that the App Center works now. We can then test whether a switch breaks anything. +++ This bug was initially created as a clone of Bug #40064 +++ Currently, the UMC App Center installs, updates, uninstalls non-docker Apps with the old Application class. It should instead use the new App class. Some work still has to go into these functions, but it would be far better to use them. No double bug fixing when a dysfunctional routine is implemented in both classes. Support of docker features like a preinst script without additional implementation effort. Startup speed increases as the App cache only needs to be loaded once. The following things do not work at the moment: Dry run - there is no package list to get before installing an app. Connection to other hosts is currently done via "ssh univention-app ...". This may be a problem for non 4.1 systems. univention-app installs directly via apt-get, not with the PackageManager class. This should not make a difference, yet it needs to be tested thoroughly.
4.2-0: r72979 | Bug #42587: ucs-test (appcenter): add 73_umc_dependency_failure 4.1-3: r72971 | Bug #42587: ucs-test (appcenter): add 73_umc_dependency_failure