Commit Graph

6 Commits

Author SHA1 Message Date
zhurong 1ea1cda5d4 Remove murano_tempest_tests from murano repo
Change-Id: I5da1c660393df335f8d5e8ab17b23bb21a8e3257
2017-12-07 02:03:48 +00:00
Felipe Monteiro 7cc0980232 Add idempotent_id decorators to murano_tempest_tests
This commit does 2 things:
  1) Adds idempotent_id decorators to murano_tempest_tests using
     check-uuid --package murano_tempest_tests --fix

  2) Fixes the external white list error that is thrown by tox -e pep8
     (which uses bandit but which was previously not included in
      whitelist_externals)

Change-Id: I8d75601a40baf5749f12151df18a116e8fab628c
2017-07-24 20:33:49 +01:00
Felipe Monteiro 634e0daa9a Update testtools.testcase.attr to decorators.attr
Tempest has moved their attr decorator to tempest.lib [0]. So now
that decortators.attr is a part of Tempest's stable library, we
should use it instead of testtools.testcase.attr, since it is
the standardized way of adding attributes to test cases in
Tempest.

This allows the possibility of doing:

    @decorators.attr(type=['foo', 'bar'])

Rather than:

    @testtools.testcase.attr('foo')
    @testtools.testcase.attr('bar')

[0] https://review.openstack.org/#/c/456236/

Change-Id: I76c23e46e57dbdbbce046f1522ed5489e5ec9d1f
2017-07-19 18:10:00 +00:00
Victor Ryzhenkin e59e9435dd Do not override credential provider in tenant isolation tests
Currently the dynamic cred provider will be overrided each time
when the dynamic crededentials were generated. It causes resource
leakage in tests which used multiple dynamic credentials
e.g tenant isolation tests.

This patch makes cred generator reuse dynamic cred provider which
used for creation of first isolated credentials for second isolated
credentials too.

Change-Id: I657d66fd7cc4463e6a97cbf25d3db0cd6ff66602
Closes-Bug: #1606987
2016-08-01 08:53:22 +00:00
Kirill Zaitsev c25f8677a2 Enable static action tests with glare backend
Change-Id: I3abeedd6edb0ef710304395d49b7b0cb0287407a
Targets: bp murano-glare-devstack-testing
2016-07-22 12:38:02 +00:00
Valerii Kovalchuk 7d186c191d Implement API call and RPC call for static actions
Static public methods can be called synchronously through the
API call without creating environment, object instances and
database records. It is proposed to make RPC call as the single
request-responce for now.
However async API and RPC calls may also be implemented later
exploiting the same pattern as for calling instance methods.
New call can be done through client method (see
Ib6a60f8e33c5d3593a55db9f758e94e27f0a4445)
Tempest and unit tests are added.

APIImpact
Implements: blueprint static-actions
Change-Id: I17ab2eba0fd6c42309667f42d0644d21940ab02d
2016-07-07 17:21:59 +00:00