aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorRoss Brattain <ross.b.brattain@intel.com>2017-12-22 10:48:33 +0000
committerGerrit Code Review <gerrit@opnfv.org>2017-12-22 10:48:33 +0000
commit6459403fbd505549f13190a28eeeb15289945850 (patch)
treebf815a555b0871474fb52aba66f04d4c2acaba18 /docs
parent03e3d755defe0c69a18b0ca46912cd90778a8abe (diff)
parent2939c61f7236c289e5f2fd828cbcb3ffb816c9c6 (diff)
Merge "Remove "flake8" and "pep8" from test-requirements"
Diffstat (limited to 'docs')
-rwxr-xr-xdocs/testing/developer/devguide/devguide.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/testing/developer/devguide/devguide.rst b/docs/testing/developer/devguide/devguide.rst
index 1d47e5605..dade49b75 100755
--- a/docs/testing/developer/devguide/devguide.rst
+++ b/docs/testing/developer/devguide/devguide.rst
@@ -361,7 +361,7 @@ Verify your patch locally before submitting
Once you finish a patch, you can submit it to Gerrit for code review. A
developer sends a new patch to Gerrit will trigger patch verify job on Jenkins
-CI. The yardstick patch verify job includes python flake8 check, unit test and
+CI. The yardstick patch verify job includes python pylint check, unit test and
code coverage test. Before you submit your patch, it is recommended to run the
patch verification in your local environment first.