diff --git a/doc/feature_request/launch_specific_benchmark.rst b/doc/feature_request/launch_specific_benchmark.rst index 312585fd..21008f52 100644 --- a/doc/feature_request/launch_specific_benchmark.rst +++ b/doc/feature_request/launch_specific_benchmark.rst @@ -23,5 +23,5 @@ would like to execute. Possible solution ----------------- -* Add optinal flag to rally task start command to specify one or more +* Add optional flag to rally task start command to specify one or more benchmarks to execute as part of that test run. \ No newline at end of file diff --git a/doc/release_notes/latest.rst b/doc/release_notes/latest.rst index f5615f64..17b56ff9 100644 --- a/doc/release_notes/latest.rst +++ b/doc/release_notes/latest.rst @@ -148,7 +148,7 @@ Bug fixes * Fix heat stacks cleanup by deleting them only 1 time per tenant (get rid of "stack not found" errors in logs). -* Fix the wrong behaviour of 'rally task detailed --iterations-data' (it lacked the iteration info before). +* Fix the wrong behavior of 'rally task detailed --iterations-data' (it lacked the iteration info before). * Fix security groups cleanup: a security group called "default", created automatically by Neutron, did not get deleted for each tenant. @@ -175,6 +175,6 @@ Documentation * Various fixes * Remove obsolete *.rst* files (*deploy_engines.rst* / *server_providers.rst* / ...) - * Restructure the docs files to make them easier to natigate through + * Restructure the docs files to make them easier to navigate through * Move the chapter on task templates to the 4th step in the tutorial * Update the information about meetings (new release meeting & time changes) diff --git a/doc/source/contribute.rst b/doc/source/contribute.rst index e543a72c..2d9e38d1 100644 --- a/doc/source/contribute.rst +++ b/doc/source/contribute.rst @@ -151,7 +151,7 @@ Functional tests *Files: /tests/functional/** The goal of `functional tests `_ is to check that everything works well together. -Fuctional tests use Rally API only and check responses without touching internal parts. +Functional tests use Rally API only and check responses without touching internal parts. To run functional tests locally:: @@ -162,9 +162,9 @@ To run functional tests locally:: #NOTE: openrc file with OpenStack admin credentials Output of every Rally execution will be collected under some reports root in -directiry structure like: reports_root/ClassName/MethodName_suffix.extension +directory structure like: reports_root/ClassName/MethodName_suffix.extension This functionality implemented in tests.functional.utils.Rally.__call__ method. -Use 'gen_report_path' method of 'Rally' class to get automaticaly generated file +Use 'gen_report_path' method of 'Rally' class to get automatically generated file path and name if you need. You can use it to publish html reports, generated during tests. Reports root can be passed throw environment variable 'REPORTS_ROOT'. Default is