cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update CODING_GUIDELINES.md

Browse source
This commit is contained in:
Michael DeHaan 2014-02-23 12:22:36 -05:00
parent c7ae1ee978
commit 7638d8ff46
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
CODING_GUIDELINES.md
View file

@ -28,11 +28,11 @@ PEP8 and basic style checks
Testing Testing
======= =======
* Much of ansible's testing needs are in integration, not unit tests. We're working on releasing wide array of integration tests that use modules in a live environment. * Much of ansible's testing needs are in integration, not unit tests. Add module tests there.
* That being said, there are unit tests * That being said, there are unit tests too!
* Code written must absolutely pass unit tests (i.e. "make tests") * Code written must absolutely pass tests (i.e. "make tests")
* You should anticipate any error paths in your code and test down those error paths. * You should anticipate any error paths in your code and test down those error paths.
* Additions to unit tests for core code is welcome, but modules tend to be more integration-testey, so it's not always possible to add them (examples: ec2, etc). * Additions to tests for core code is welcome, but not always possible. Be sure things are at least well tested manually in that case.
Whitespace Whitespace
========== ==========