diff options
Diffstat (limited to 'docs/testing/user')
| -rw-r--r-- | docs/testing/user/configguide/configguide.rst | 6 | ||||
| -rw-r--r-- | docs/testing/user/userguide/index.rst | 8 |
2 files changed, 7 insertions, 7 deletions
diff --git a/docs/testing/user/configguide/configguide.rst b/docs/testing/user/configguide/configguide.rst index 61fc4593..083bbf3a 100644 --- a/docs/testing/user/configguide/configguide.rst +++ b/docs/testing/user/configguide/configguide.rst @@ -283,7 +283,7 @@ to attach the 'Up' status Functest container and start bash mode:: docker exec -it <Functest_Container_Name> bash -4, Functest environemnt preparation and check +4, Functest environment preparation and check To see the Section below `Preparing the Functest environment`_. @@ -417,7 +417,7 @@ We may distinguish several directories, the first level has 4 directories: profile or any other test inputs that could be reused by any test project. * **docker**: This directory includes the needed files and tools to - build the Funtest Docker image. + build the Functest Docker image. * **docs**: This directory includes documentation: Release Notes, User Guide, Configuration Guide and Developer Guide. * **functest**: This directory contains all the code needed to run @@ -513,7 +513,7 @@ This script will make sure that the requirements to run the tests are met and will install the needed libraries and tools by all Functest test cases. It should be run only once every time the Functest docker container is started from scratch. If you try to run this command, on -an already prepared enviroment, you will be prompted whether you really +an already prepared environment, you will be prompted whether you really want to continue or not:: functest env prepare diff --git a/docs/testing/user/userguide/index.rst b/docs/testing/user/userguide/index.rst index c1faecda..5268559b 100644 --- a/docs/testing/user/userguide/index.rst +++ b/docs/testing/user/userguide/index.rst @@ -198,7 +198,7 @@ updates the appropriate parameters into the configuration file. When the Tempest suite is executed, each test duration is measured and the full console output is stored to a *log* file for further analysis. -The Tempest testcases are distributed accross two +The Tempest testcases are distributed across two Tiers: * Smoke Tier - Test Case 'tempest_smoke_serial' @@ -239,7 +239,7 @@ The OPNFV Rally scenarios are based on the collection of the actual Rally scenar A basic SLA (stop test on errors) has been implemented. -The Rally testcases are distributed accross two Tiers: +The Rally testcases are distributed across two Tiers: * Smoke Tier - Test Case 'rally_sanity' * Components Tier - Test case 'rally_full' @@ -416,11 +416,11 @@ The list of tests can be described as follows: * Delete operations * Delete the port previously created via OpenStack - * Check that the port has been also succesfully deleted in OpenDaylight + * Check that the port has been also successfully deleted in OpenDaylight * Delete previously subnet created via OpenStack * Check that the subnet has also been successfully deleted in OpenDaylight * Delete the network created via OpenStack - * Check that the network has also been succesfully deleted in OpenDaylight + * Check that the network has also been successfully deleted in OpenDaylight Note: the checks in OpenDaylight are based on the returned HTTP status code returned by OpenDaylight. |