diff options
| author | Michael DeHaan <michael.dehaan@gmail.com> | 2014-02-23 12:22:36 -0500 |
|---|---|---|
| committer | Michael DeHaan <michael.dehaan@gmail.com> | 2014-02-23 12:22:36 -0500 |
| commit | 7638d8ff4637d09eef3571879a54dd7353d55f86 (patch) | |
| tree | ac2e75276a957e856c480c2b0dad42ce4eb0f25b /CODING_GUIDELINES.md | |
| parent | c7ae1ee978591e3740ddc71c7a496d7746b2311c (diff) | |
| download | ansible-7638d8ff4637d09eef3571879a54dd7353d55f86.tar.gz | |
Update CODING_GUIDELINES.md
Diffstat (limited to 'CODING_GUIDELINES.md')
| -rw-r--r-- | CODING_GUIDELINES.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/CODING_GUIDELINES.md b/CODING_GUIDELINES.md index 6a3c497d48..7860fb2481 100644 --- a/CODING_GUIDELINES.md +++ b/CODING_GUIDELINES.md @@ -28,11 +28,11 @@ PEP8 and basic style checks 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. - * That being said, there are unit tests - * Code written must absolutely pass unit tests (i.e. "make tests") + * Much of ansible's testing needs are in integration, not unit tests. Add module tests there. + * That being said, there are unit tests too! + * 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. - * 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 ========== |