summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTaseer <taseer94@gmail.com>2017-03-27 13:33:51 +0500
committerTaseer <taseer94@gmail.com>2017-03-27 18:51:38 +0500
commitee667225c20ded7d6dbfc38e8631fc96cc0dea2a (patch)
tree053f4f94c21427c8ecee94a9908540f1dfb66fe2
parent1dce84474538f1bdbba604bd4312793e3f57acf6 (diff)
Add info about selective running
Change-Id: Ic5f7969c3d3969b7790d17beec10d73991ca8d08 Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
-rw-r--r--docs/testing/user/userguide/cli.rst6
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