rpms/cockpit
5
0
Fork 0
Code Issues Pull Requests Releases Activity
15c2932687
cockpit/tests/tests.yml

33 lines
592 B
YAML
Raw Normal View History

Initial smoke tests run from upstream Cockpit project Later once the upstream no longer uses phantomjs, we should be able to execute the entire integration test suite. This includes the standard-test-overlay role, and the standard-test-scripts role. These will be suggested to the standard-test-roles repo.
2017-09-20 22:26:20 +00:00
---
- hosts: localhost
roles:
- role: standard-test-source
tags:
- always
Fix CI pipeline test - Move from the deprecated standard-test-scripts to the better supported standard-test-basic. This can install test dependencies. - Drop the obsolete standard-test-overlay, it does not even exist any more. - Drop test-canary. This was being used to test the CI gating, but this has been done now.
2018-07-28 09:51:03 +00:00
- role: standard-test-basic
Initial smoke tests run from upstream Cockpit project Later once the upstream no longer uses phantomjs, we should be able to execute the entire integration test suite. This includes the standard-test-overlay role, and the standard-test-scripts role. These will be suggested to the standard-test-roles repo.
2017-09-20 22:26:20 +00:00
tags:
- atomic
- classic
Fix CI pipeline test - Move from the deprecated standard-test-scripts to the better supported standard-test-basic. This can install test dependencies. - Drop the obsolete standard-test-overlay, it does not even exist any more. - Drop test-canary. This was being used to test the CI gating, but this has been done now.
2018-07-28 09:51:03 +00:00
required_packages:
- cockpit
Run initial upstream integration test check-menu is a very robust test that also does not change the host too much. This does not cover a lot of functionality to actually find regressions in subsystems, but exposes the missing pieces for running more integration tests in the dist-git pipeline. Re-use the cockpit/tests container for this, which has the necessary test dependencies -- most importantly, chromium-browser. Aside from not being available in RHEL, this also better shields the tests from the tested system. The container talks to Cockpit on the host, i. e. the container's gateway. Use a fixed tag to avoid running into failures with "latest", as we don't gate container updates on the dist-git tests for now.
2018-11-14 08:40:02 +00:00
- cockpit-tests
- cockpit-dashboard
tests: Run firewall tests As the firewalld tests expect the libvirt "default" network, add cockpit-machines test dependency, which pulls in the libvirt stack. We will soon test the Machines page anyway.
2020-03-23 22:38:53 +00:00
- cockpit-machines
tests: Run more browser tests Upstream now grows more and more @nondestructive test, which we can run in our single test VM, so add the first batch. This uncovers some issues in the tests that assume that there is no root login in the VM, skip them. They are being fixed in https://github.com/cockpit-project/cockpit/pull/13773
2020-03-23 11:15:45 +00:00
- cockpit-sosreport
- cockpit-storaged
tests: Enable some PackageKit tests
2020-04-01 18:51:47 +00:00
- createrepo_c
tests: Fix PackageKit tests
2020-04-06 18:24:49 +00:00
- dnf-automatic
tests: Run firewall tests As the firewalld tests expect the libvirt "default" network, add cockpit-machines test dependency, which pulls in the libvirt stack. We will soon test the Machines page anyway.
2020-03-23 22:38:53 +00:00
- firewalld
- libvirt-daemon-config-network
Run initial upstream integration test check-menu is a very robust test that also does not change the host too much. This does not cover a lot of functionality to actually find regressions in subsystems, but exposes the missing pieces for running more integration tests in the dist-git pipeline. Re-use the cockpit/tests container for this, which has the necessary test dependencies -- most importantly, chromium-browser. Aside from not being available in RHEL, this also better shields the tests from the tested system. The container talks to Cockpit on the host, i. e. the container's gateway. Use a fixed tag to avoid running into failures with "latest", as we don't gate container updates on the dist-git tests for now.
2018-11-14 08:40:02 +00:00
- podman
tests: Fix and enable testSessionRecordingShell
2020-04-01 20:24:38 +00:00
- tlog
Initial smoke tests run from upstream Cockpit project Later once the upstream no longer uses phantomjs, we should be able to execute the entire integration test suite. This includes the standard-test-overlay role, and the standard-test-scripts role. These will be suggested to the standard-test-roles repo.
2017-09-20 22:26:20 +00:00
tests:
Fix CI pipeline test - Move from the deprecated standard-test-scripts to the better supported standard-test-basic. This can install test dependencies. - Drop the obsolete standard-test-overlay, it does not even exist any more. - Drop test-canary. This was being used to test the CI gating, but this has been done now.
2018-07-28 09:51:03 +00:00
- smoke:
dir: ./source/tools/debian/tests/
run: ./smoke
Run initial upstream integration test check-menu is a very robust test that also does not change the host too much. This does not cover a lot of functionality to actually find regressions in subsystems, but exposes the missing pieces for running more integration tests in the dist-git pipeline. Re-use the cockpit/tests container for this, which has the necessary test dependencies -- most importantly, chromium-browser. Aside from not being available in RHEL, this also better shields the tests from the tested system. The container talks to Cockpit on the host, i. e. the container's gateway. Use a fixed tag to avoid running into failures with "latest", as we don't gate container updates on the dist-git tests for now.
2018-11-14 08:40:02 +00:00
- verify:
dir: .
run: ./verify.sh
tests: Sync with downstream RHEL
2019-07-30 09:07:45 +00:00
save-files: ["logs/*"]
Reference in New Issue Copy Permalink