Add ability to delete arbitrary component in functional tests
Patch adds no-arguments mode to delete_component() method. It means
that if no component_name is provided as an argument, an arbitrary
component of the env will be deleted. For most test cases the exact
component to delete doesn't matter. It allows to get rid of finding
component's id by its name and thus simplify the action a bit.
Hopefully it will make tests that use this method more reliable.
Reviewed: https:/ /review. openstack. org/368175 /git.openstack. org/cgit/ openstack/ murano- dashboard/ commit/ ?id=3b04e2068b0 ddb6b25fbaaf8eb 26b3f53da6e58e
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3b04e2068b0ddb6 b25fbaaf8eb26b3 f53da6e58e
Author: Valerii Kovalchuk <email address hidden>
Date: Fri Sep 9 21:11:35 2016 +0300
Add ability to delete arbitrary component in functional tests
Patch adds no-arguments mode to delete_component() method. It means
that if no component_name is provided as an argument, an arbitrary
component of the env will be deleted. For most test cases the exact
component to delete doesn't matter. It allows to get rid of finding
component's id by its name and thus simplify the action a bit.
Hopefully it will make tests that use this method more reliable.
Change-Id: If32a8691701349 a173522fed22e88 f40e21784cd
Related-bug: #1618118