You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docsite/rst/community/development_process.rst
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -232,14 +232,12 @@ Testing PRs
232
232
233
233
Adding tests for your PR makes it a stronger candidate for being merged.
234
234
235
-
PRs that add new functionality should include tests to fully exercise the new functionality and the failure paths of that functionality.
236
-
Bugfix PRs should include tests that ensure the bug is no longer present.
237
-
As a rule of thumb, integration tests should be preferred over unit tests.
238
-
239
235
For information on writing integration tests, see the docs page on :ref:`Integration tests <testing_integration>` and the existing integration tests at `test/integration <https://github.com/ansible/ansible/tree/devel/test/integration/targets>`_.
240
236
241
237
For information on writing unit tests see the docs page on :ref:`Unit tests <testing_units>` and the existing unit tests at `test/units <https://github.com/ansible/ansible/tree/devel/test/units>`_.
242
238
239
+
If you are not sure how to proceed with writing tests, ask for clarification in any of our :ref:`community channels. <communication>`
0 commit comments