This website requires JavaScript.
Explore
Help
Sign In
rpms
/
cockpit-podman
Watch
7
Star
0
Fork
0
You've already forked cockpit-podman
Code
Issues
Pull Requests
Releases
Activity
195e8547d2
cockpit-podman
/
tests
/
tests.yml
7 lines
65 B
YAML
Raw
Normal View
History
Unescape
Escape
Add initial upstream integration test 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
2020-04-15 05:34:03 +00:00
---
-
hosts
:
localhost
Move the test into a role 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
2020-05-19 06:57:54 +00:00
tags
:
tests.yml: Fix tags "always" is not a thing in the current spec [1]. [1] https://docs.fedoraproject.org/en-US/ci/standard-test-interface/#_invocation
2020-07-15 06:53:17 +00:00
-
classic
Move the test into a role 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
2020-05-19 06:57:54 +00:00
roles
:
-
test
Reference in New Issue
Copy Permalink