From 26050562ca8a9a8a00a1d57ba2820f5275df0eef Mon Sep 17 00:00:00 2001 From: lilintan Date: Wed, 31 Aug 2016 10:01:45 +0800 Subject: [PATCH] TrivialFix: Modify the spelling mistake Change-Id: I07bd96de0dd1f89b66b3a4fd2bed0f222c237fb8 --- TESTING.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TESTING.rst b/TESTING.rst index fb25f646fd5..e4f44642cd3 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