diff options
| -rw-r--r-- | docs/testing/user/userguide/cli.rst | 6 | ||||
| -rw-r--r-- | test-requirements.txt | 9 |
2 files changed, 9 insertions, 6 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 diff --git a/test-requirements.txt b/test-requirements.txt index cfbbdcdd..5b770010 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -2,15 +2,12 @@ # of appearance. Changing the order has an impact on the overall integration # process, which may cause wedges in the gate later. -tox -pytest -pytest-cov -pytest-mock coverage -pykwalify mock pip_check_reqs -coverage +pykwalify +pytest pytest-cov pytest-faker +pytest-mock tox |