cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
ansible/test
History
Dag Wieers 72e7927dd5 win_scheduled_task: Added frequency: once and check_mode support (#22611) 
* win_scheduled_task: Added frequency: once and check_mode support

This patch includes:
- Renamed `execute:` parameter to `executable:`
- Renamed `argument:` parameter to `arguments:`
- Implemented `frequency: once` support
- Implemented check_mode support
- Fix idempotency issue related to empty description
- Added integration tests

* Improve the integration test structure

I think this is a great way to test normal mode and check-mode from the same playbook.

* Small fixes after review
2017-03-15 07:11:24 -07:00
..
compile Use lint friendly output for python syntax checks. (#22390) 2017-03-07 20:27:50 -08:00
integration win_scheduled_task: Added frequency: once and check_mode support (#22611) 2017-03-15 07:11:24 -07:00
results Create bot friendly sanity output. (#22381) 2017-03-07 14:59:50 -08:00
runner Add --failure-ok option to ansible-test. (#22623) 2017-03-14 16:32:21 -07:00
sanity New metadata 1.0 (#22587) 2017-03-14 09:07:22 -07:00
units Implement eos_banner for EAPI (#22609) 2017-03-14 21:00:17 +01:00
utils Add --failure-ok option to ansible-test. (#22623) 2017-03-14 16:32:21 -07:00
README.md Switch tests to pytest and ansible-test. 2017-01-11 12:34:59 -08:00

README.md

Ansible Test System

Folders

units

Unit tests that test small pieces of code not suited for the integration test layer, usually very API based, and should leverage mock interfaces rather than producing side effects.

Playbook engine code is better suited for integration tests.

Requirements: sudo pip install paramiko PyYAML jinja2 httplib2 passlib nose pytest mock

integration

Integration test layer, constructed using playbooks.

Some tests may require cloud credentials, others will not, and destructive tests are separated from non-destructive so a subset can be run on development machines.

learn more

hop into a subdirectory and see the associated README.md for more info.