diff options
author | Taseer <taseer94@gmail.com> | 2017-03-27 13:33:51 +0500 |
---|---|---|
committer | Yujun Zhang <zhang.yujunz@zte.com.cn> | 2017-03-28 06:16:33 +0000 |
commit | 6c185f6a4541e81d1ea8124f9b8d126d60679e6f (patch) | |
tree | ba924c2c2ede29d7753d6a918628d11cb95c3eb9 /docs | |
parent | cdc3d2a50bb02f2e68e7f497ae73bbb80ba8db35 (diff) |
Add info about selective running
Change-Id: Ic5f7969c3d3969b7790d17beec10d73991ca8d08
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
(cherry picked from commit ee667225c20ded7d6dbfc38e8631fc96cc0dea2a)
Diffstat (limited to 'docs')
-rw-r--r-- | docs/testing/user/userguide/cli.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/testing/user/userguide/cli.rst b/docs/testing/user/userguide/cli.rst index 19420bd1..96026c5b 100644 --- a/docs/testing/user/userguide/cli.rst +++ b/docs/testing/user/userguide/cli.rst @@ -38,6 +38,12 @@ as above. An important thing to remember is to provide absolute path of result d qtip plan run <plan_name> -p $PWD/result Similarly, the same commands can be used for the other two components making up the plans, i.e QPI's and metrics. +For example, in order to run a single metric +:: + + qtip metric run <metric_name> -p $PWD/result + +The same can be applied for a QPI. QTIP also provides the utility to view benchmarking results on the console. One just need to provide to where the results are stored. Extending the example above |