So that it can be called from the container-tools module without
duplication. For technical reasons this requires calling the test entry
script from a different directory, so parameterize it.
Rename the test from "browser" to "cockpit-podman" so that it is
more descriptive within a module test.
Drop the TEST_OS hack, tests of current version recognizes RHEL 8.3 just
fine (and in fact depends on it).
Related: rhbz#1821193
- Restyle buttons and dropdowns to be consistent with Cockpit
- Disable button and show a spinner while delete operation is in progress
- Translation updates
Add a gating.yaml to make sure that newer cockpit-podman versions don't
enter stable when they cause regressions in various static RPM checks or
our CI tests.
See https://docs.pagure.org/greenwave/policies.html
Re-use the test skeleton from cockpit. Just run a single integration
test for now, until we make them properly @nondestructive upstream [1].
Run chromium and the test directly on the test bed. For cockpit-podman
tests it's not practical to run them in a cockpit/tasks podman
container, as that container interferes too much with the tests.
[1] https://github.com/cockpit-project/cockpit-podman/pull/356
- Fix Alert notification in Image Search Modal
- Allow more than a single Error Notification for Container action errors
- Various Alert cleanups
- Translation updates
- Enable Commit button for running containers
- Fix race condition with container deletion
- Stop fetching all containers/images for each container/image event
