@@ -32,6 +32,10 @@ A module's design should anticipate upgrades to the services it provides. Config
32
32
33
33
A module should be designed and implemented to run as quickly as possible in order to minimize the time to run an entire playbook or even the role itself. A small performance penalty here and a small penalty there eventually adds to a very slow deployment system. Performance is important.
34
34
35
+### Tests
36
+
37
+A module should have tests. TBD: more about this and what the expectation is.
38
+
35
39
## Design checklist
36
40
37
41
Consider the following checklist when reviewing a module's design.