openstack
/
tempest
Code Issues Proposed changes

Use data_utils in tempest.lib.common.utils 

Tempest tests should use the stable method defined in tempest.lib.
This patch is to use data_utils from tempest.lib.common.utils in
OAUTHConsumersV3Test and HACKING.rst.

Change-Id: Ia9f4cf37d8d57da34864a5eb55a8fe9d9c5722f5
This commit is contained in:
jeremy.zhang 2017-05-26 13:41:57 +08:00
parent 7203f58c97
commit c0f9556c7a
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
HACKING.rst
View File

@ -232,9 +232,9 @@ parallel.
and xml version of the same test class there could still be a race between
methods.
- The rand_name() function from tempest.common.utils.data_utils should be used
anywhere a resource is created with a name. Static naming should be avoided
to prevent resource conflicts.
- The rand_name() function from tempest.lib.common.utils.data_utils should be
used anywhere a resource is created with a name. Static naming should be
avoided to prevent resource conflicts.
- If the execution of a set of tests is required to be serialized then locking
can be used to perform this. See AggregatesAdminTest in

2
tempest/api/identity/admin/v3/test_oauth_consumers.py
View File

@ -14,7 +14,7 @@
# under the License.
from tempest.api.identity import base
from tempest.common.utils import data_utils
from tempest.lib.common.utils import data_utils
from tempest.lib.common.utils import test_utils
from tempest.lib import decorators
from tempest.lib import exceptions as exceptions