summaryrefslogtreecommitdiffstats
path: root/docs/testing/developer/devguide/devguide.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/testing/developer/devguide/devguide.rst')
-rwxr-xr-xdocs/testing/developer/devguide/devguide.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/testing/developer/devguide/devguide.rst b/docs/testing/developer/devguide/devguide.rst
index 4f69456fc..dade49b75 100755
--- a/docs/testing/developer/devguide/devguide.rst
+++ b/docs/testing/developer/devguide/devguide.rst
@@ -123,9 +123,9 @@ In this Yaml file, you can easily find it consists of two sections. One is “Sc
context:
name: demo
- image: cirros-0.3.5
+ image: yardstick-image
flavor: yardstick-flavor
- user: cirros
+ user: ubuntu
placement_groups:
pgrp1:
@@ -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.