1ce92bf34d
Currently create_user is just inherited from CredsClient and, therefore, does not pass a domain_id to the /v3/users POST API call to create a new user. As a result a domain with id "default" is used as no domain is explicitly passed in the API call which results in 404 NOT FOUND and the following error: "Could not find domain: default.". The right way is passing a domain from: 1) CONF.auth.admin_domain_name 2) CONF.auth.default_credentials_domain_name This is already taken into account when a domain_name is passed from identity_utils during object instantiation and used for in the create_project method specific to V3CredsClient. The API calls only accept a domain_id which is why creds_domain field of a V3CredsClient object is used to store an id of a domain_name domain passed via constructor. The same can be used for create_user method specific to v3. Change-Id: I66f22c61d7a8596cafdc415654edfecdc5495d2e Closes-Bug: #1613819
Tempest Field Guide Overview
Tempest is designed to be useful for a large number of different environments. This includes being useful for gating commits to OpenStack core projects, being used to validate OpenStack cloud implementations for both correctness, as well as a burn in tool for OpenStack clouds.
As such Tempest tests come in many flavors, each with their own rules and guidelines. Below is the overview of the Tempest repository structure to make this clear.
tempest/
api/ - API tests
scenario/ - complex scenario tests
tests/ - unit tests for Tempest internalsEach of these directories contains different types of tests. What belongs in each directory, the rules and examples for good tests, are documented in a README.rst file in the directory.
api_field_guide
API tests are validation tests for the OpenStack API. They should not use the existing Python clients for OpenStack, but should instead use the Tempest implementations of clients. Having raw clients let us pass invalid JSON to the APIs and see the results, something we could not get with the native clients.
When it makes sense, API testing should be moved closer to the projects themselves, possibly as functional tests in their unit test frameworks.
scenario_field_guide
Scenario tests are complex "through path" tests for OpenStack functionality. They are typically a series of steps where complicated state requiring multiple services is set up exercised, and torn down.
Scenario tests should not use the existing Python clients for OpenStack, but should instead use the Tempest implementations of clients.
unit_tests_field_guide
Unit tests are the self checks for Tempest. They provide functional verification and regression checking for the internal components of Tempest. They should be used to just verify that the individual pieces of Tempest are working as expected.