ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Test placement (#21801)

Browse source 
* Fix test placement and update messaging.
* Add note about group selection.
This commit is contained in:
Matt Clay 2017-02-22 12:43:45 -08:00 committed by GitHub
parent b5e0eb0985
commit cba91c7f44
10 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

0
test/integration/targets/cloudscale_server/defaults/main.yml → test/integration/roles/cloudscale_server/defaults/main.yml
View file

0
test/integration/targets/cloudscale_server/meta/main.yml → test/integration/roles/cloudscale_server/meta/main.yml
View file

0
test/integration/targets/cloudscale_server/tasks/main.yml → test/integration/roles/cloudscale_server/tasks/main.yml
View file

0
test/integration/targets/cnos_vlan/README.md → test/integration/roles/cnos_vlan/README.md
View file

0
test/integration/targets/cnos_vlan/cnos_vlan_sample_hosts → test/integration/roles/cnos_vlan/cnos_vlan_sample_hosts
View file

0
test/integration/targets/cnos_vlan/tasks/main.yml → test/integration/roles/cnos_vlan/tasks/main.yml
View file

0
test/integration/targets/cnos_vlan/vars/main.yml → test/integration/roles/cnos_vlan/vars/main.yml
View file

0
test/integration/targets/cloudscale_server/aliases
View file

0
test/integration/targets/cnos_vlan/aliases
View file

10
test/sanity/code-smell/integration-aliases.py
View file

@ -46,12 +46,20 @@ def main():
%s %s
Unless a test cannot run as part of CI, you'll want to add an appropriate CI alias, such as: If these tests cannot be run as part of CI (requires external services, unsupported dependencies, etc.),
then they most likely belong in `test/integration/roles/` instead of `test/integration/targets/`.
In that case, do not add an `aliases` file. Instead, just relocate the tests.
However, if you think that the tests should be able to be supported by CI, please discuss test
organization with @mattclay or @gundalow on GitHub or #ansible-devel on IRC.
If these tests can be run as part of CI, you'll need to add an appropriate CI alias, such as:
posix/ci/group1 posix/ci/group1
windows/ci/group2 windows/ci/group2
The CI groups are used to balance tests across multiple jobs to minimize test run time. The CI groups are used to balance tests across multiple jobs to minimize test run time.
Using the relevant `group1` entry is fine in most cases. Groups can be changed later to redistribute tests.
Aliases can also be used to express test requirements: Aliases can also be used to express test requirements: