openstack/qa-specs
Code Issues Proposed changes

Fix some spelling typo in manual

Browse Source 
neccessary -> necessary
successfull -> successful
existance -> existence
specifc -> specific
dependancies -> dependencies

Change-Id: I5a316432b441561e173785f7bf24f9ba4280d06f
Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
This commit is contained in:
Zhao Lei
2015-09-24 20:57:14 +08:00
parent fb7a672a40
commit 55d3c12fc4
5 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
specs/tempest/implemented/branchless-tempest-extensions.rst
View File

@@ -43,7 +43,7 @@ This would imagine a world where the definition would look as follows
icehouse: icehouse:
compute-ext: [floating-ips, aggregates, ... ] compute-ext: [floating-ips, aggregates, ... ]
The non existance of an extensions list means assume 'all'. It is also The non existence of an extensions list means assume 'all'. It is also
expected that you'd be able to specify 'rm-compute-ext' much like expected that you'd be able to specify 'rm-compute-ext' much like
rm-services, so that you could do something as follows. rm-services, so that you could do something as follows.
:: ::

2
specs/tempest/implemented/meta-data-and-uuid-for-tests.rst
View File

@@ -132,4 +132,4 @@ Work Items
Dependencies Dependencies
============ ============
- No known external dependancies. - No known external dependencies.

2
specs/tempest/implemented/resource-cleanup.rst
View File

@@ -83,7 +83,7 @@ attributes defined during setUpClass, which may not be there anymore.
Disallow overriding ``tearDownClass`` defined in ``BaseTestCase`` with Disallow overriding ``tearDownClass`` defined in ``BaseTestCase`` with
an hacking rule. Define ``tearDownClass`` so that it invokes a descendant an hacking rule. Define ``tearDownClass`` so that it invokes a descendant
specifc cleanup code, and finally cleans-up credentials. specific cleanup code, and finally cleans-up credentials.
:: ::

2
specs/tempest/ipv6-api-testing-parity.rst
View File

@@ -18,7 +18,7 @@ Problem description
=================== ===================
IPv6 is evolving in Neutron and the community is working hard to add the IPv6 is evolving in Neutron and the community is working hard to add the
neccessary support. However, the current API tests in tempest do not necessary support. However, the current API tests in tempest do not
validate IPv6 to the same extent as IPv4. validate IPv6 to the same extent as IPv4.
Also, Neutron now supports two extended attributes for IPv6 subnets Also, Neutron now supports two extended attributes for IPv6 subnets

2
specs/tempest/stress-api-tracking.rst
View File

@@ -42,7 +42,7 @@ Example expected (and configurable) whitelisted methods could include:
For each decorated method, maintain a dictionary that tracks: For each decorated method, maintain a dictionary that tracks:
#. The number of successfull calls #. The number of successful calls
#. The number of failed calls #. The number of failed calls
#. The list of observed stacktraces for the failed calls #. The list of observed stacktraces for the failed calls