orchestration_client is recently moved from tempest
to murano-tempest-plugin but there is one import error
and instantiation of orchestration_client. Fixing the
error.
Change-Id: I0743a6c1e9a97740aa5e5cb7f10bc0f06aabbf05
orchestration_client in Tempest is planned to be removed and heat
client present in heat_tempest_plugin is supposed to be used
- ba43685c13/heat_tempest_plugin/services/clients.py (L103)
Meanwhile murano_tempest_plugin is the only user of tempest orchestration_client
so moving that here and it can be removed once murano switch to use
client from heat_tempest_plugin.
Change-Id: I8f160c6b9b59d6915d6fb346be7816b4b8084939
Congress has been retired and requirements-check fails now, remove
congress.
See also https://review.opendev.org/721741
Change-Id: Ic2d74543f65a60ccb567aae4c4012c422884bb50
The repo is Python 3 now, so update hacking to version 2.0 which
supports Python 3.
Fix problems found.
Update local hacking checks for new flake8.
Change-Id: I2683bc1a7c962da137de4b77aac450f08d1f6c4a
In scenario test, test packages will be uploaded and then deleted after test
executed. But in case of the packages deletion failure, it will block the
following tests.
This patch checks and removes those test packages before uploading them.
Change-Id: I90c5d903d8c5c3eeface2735bba61d01a877aaf8
* tempest.lib.decorators provides a better way to handle attrs, let's
use it instead of using nose from tempest.lib stable api.
Change-Id: Iad64bbaac517b8e1f53ec7046691a79e63f4f74d
Since I1c02fd88c3d93b511ff4a6b54b668ebd306481a9 this commit
Remove deprecated 'orchestration' config group options,
cause the error in murano tempest test:
tempest.lib.exceptions.UnknownServiceClient: Service clients named orchestration are not known
we should add those config in murano tempest.
Change-Id: I5cd674b94ee472c5b5ab6a9a51170d89880887a4
apt-get update should be performed first before installing the
debian packages, otherwise it may breaks during the application
script execution in tests.
Change-Id: I0c2e35fe1c05182ab7a9db094f787df9a8df1248
Since Idd6c6be1c8bdf4dcf730f67e75a58a0329fe5259 this commit add the
jsonschema validation for backup restore, restore a volume using null
name or uuid will failed. This breaks the original process.
So we skip this test, when it fixed, revert this patch.
Change-Id: Iaba14c48e1a4f7d837df4a9881953d2cfa311545
Added tests for following scenarios:
* deploy session
* list all deployments
* list deployments (in a specific environment)
* list a specific deployment's statuses
Added application_catalog_client methods for following functionality:
* list all deployments
* list deployments (in a specific environment)
* list a specific deployment's statuses
Change-Id: I0ac1b2a6216fd1794ba06ee0b26e6c2c90118526
Added tests for following scenarios:
* publicize a non-public package
* publicize a package as non-admin user (negative test)
Change-Id: I0c2ef75535cdd894ce30d1c1404ce964ec00b248
Added negative tests for the scenarios:
* Abandon environment with invalid id
* Update environment with invalid id
Change-Id: I19d37cd0664a5faa789f79f1163c701316bf890d
If Cinder is not available or Cinder v1 only is available skip
volume attachment tests. Else prefer volume v3 where available
or fallback to v2 otherwise.
This requires a Tempest patch for the snapshots v3 client.
Change-Id: If3b6a2c71498c19a0a8dfeb4c51e2c80e5a918f4
Depends-on: I21f07f7b3e8f22055e7978c0bf4aa01b80b493d9
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
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
Tempest will not be initialising the orchestration client by default
anymore since Heat is not a service hosted in Tempest (for a long time now).
The client is still available in Tempest (as long as it's not made
available by heat somewhere else), so to use it it's enough to pass it's
configuration to it.
This was partly fixed in Ic6fef4b4f260d13efd7b035bc012369f0da55602 but
the patch was not complete.
Change-Id: Iba1680276fec776a81f1e91fd591137e39bf6d07
Tempest will not be initialising the orchestration client by default
anymore since Heat is not a service hosted in Tempest (for a long time now).
The client is still available in Tempest (as long as it's not made
available by heat somewhere else), so to use it it's enough to pass it's
configuration to it.
Change-Id: Ic6fef4b4f260d13efd7b035bc012369f0da55602
1.Unskip test_deploy_app_with_volume_creation test
2.change flavor from m1.small to m1.tiny, to reduce the
test failing chances.
Closes-Bug: #1701230
Change-Id: Ib996bf50e1b7d542b98cf9d7125b824771c143d6
The tempest test is currently broken and blocks the gate.
This commit adds expectedFailure decorator around it.
So when the bug is fixed we would not forget to unskip the test.
Change-Id: Id3adbf59e116e2d73c74e782a345c7ca8d6fa41e
Related-Bug: #1701230
The API catalog endpoint `show_categories` was deprecated back
in Liberty cycle. It should be removed.
This commit removes the deprecated endpoint `show_categories`,
removes it from the API router, and removes references to it
in Tempest tests -- which now test `list_categories` instead.
Change-Id: If1bea7448c0d4aa5fdf37c8400323589d73fdb21
While Tempest's own plugin documentation recommends that
plugins only consume tempest.lib [0], the BaseTestCase in
tempest.test is more feature-rich, comprehensive, and fault-tolerant
than the BaseTestCase in tempest.lib.
Many plugins like keystone_tempest_plugin already use the
BaseTestCase in tempest.test. Also, QA PTL said it would be
fine to make the transition when asked in IRC [1][2].
This commit specifically:
- uses the base tempest class pattern specified in
`tempest.test.BaseTestCase`: skip_checks for skipping tests based
on environment config settings; setup_clients for instantiating
clients and client managers; resource_setup for setting up
class-level resources; and resource_cleanup for cleaning up
class-level resources
- removes unusued helpers like verify_nonempty, except in classes
that explicitly already use it
- removes clearing credentials in tearDown because the code isn't
even executed due to a bug introduced by
I51434685555c1da92401891a60285bf52571b8b5
- separate admin clients from non-admin clients by using os_admin
vs os_primary
[0] https://docs.openstack.org/developer/tempest/plugin.html#plugin-structure
[1] http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2017-06-12.log.html#t2017-06-12T20:38:19
[2] http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2017-06-12.log.html#t2017-06-12T21:45:56
Change-Id: Ia09dbc52ba13ca822a539e509e0e517592435aec
1.As mentioned in [1], we should avoid using six.iteritems to achieve
iterators. We can use dict.items instead, as it will return iterators
in PY3 as well. And dict.items/keys will more readable.
2.In py2, the performance about list should be negligible, see the
link [2].
[1] https://wiki.openstack.org/wiki/Python3
[2] http://lists.openstack.org/pipermail/openstack-dev/2015-June/066391.html
Change-Id: I45fa65427318e1c35bb521de46e81ea12ca7b770