diff options
| author | lilintan <lintan.li@easystack.cn> | 2016-08-31 10:01:45 +0800 |
|---|---|---|
| committer | lilintan <lintan.li@easystack.cn> | 2016-10-27 11:52:17 +0000 |
| commit | 26050562ca8a9a8a00a1d57ba2820f5275df0eef (patch) | |
| tree | 9eddad9b2d30fc1ad7124e9c42caac5bebd05542 /TESTING.rst | |
| parent | 5f1994dd7996907614b4ca49e3b5c21ded4d543f (diff) | |
| download | neutron-26050562ca8a9a8a00a1d57ba2820f5275df0eef.tar.gz | |
TrivialFix: Modify the spelling mistake
Change-Id: I07bd96de0dd1f89b66b3a4fd2bed0f222c237fb8
Diffstat (limited to 'TESTING.rst')
| -rw-r--r-- | TESTING.rst | 2 |
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 |