Merge "Document for Euphrates test case results"

[yardstick.git] / docs / testing / developer / devguide / devguide.rst

diff --git a/docs/testing/developer/devguide/devguide.rst b/docs/testing/developer/devguide/devguide.rst
index da7629a..04d5350 100755 (executable)
--- 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.
 
@@ -372,7 +372,7 @@ directory using the ``cd`` command. Assume that ``YARDSTICK_REPO_DIR`` is the pa
 
 Verify your patch::
 
-  ./run_tests.sh
+  tox
 
 It is used in CI but also by the CLI.
 
@@ -432,7 +432,8 @@ Yardstick committers and contributors to review your codes.
    :width: 800px
    :alt: Gerrit for code review
 
-You can find Yardstick people info `here <https://wiki.opnfv.org/display/yardstick/People>`_.
+You can find a list Yardstick people `here <https://wiki.opnfv.org/display/yardstick/People>`_,
+or use the ``yardstick-reviewers`` and ``yardstick-committers`` groups in gerrit.
 
 Modify the code under review in Gerrit
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^