summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--TESTING.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/TESTING.rst b/TESTING.rst
index fb25f646fd..e4f44642cd 100644
--- a/TESTING.rst
+++ b/TESTING.rst
@@ -31,7 +31,7 @@ There's two ways to approach testing:
1) Write unit tests because they're required to get your patch merged.
This typically involves mock heavy tests that assert that your code is as
written.
-2) Putting as much thought in to your testing strategy as you do to the rest
+2) Putting as much thought into your testing strategy as you do to the rest
of your code. Use different layers of testing as appropriate to provide
high *quality* coverage. Are you touching an agent? Test it against an
actual system! Are you adding a new API? Test it for race conditions