Added support for scenario-based flavor creation. 77/29877/5
authorspisarski <s.pisarski@cablelabs.com>
Mon, 6 Mar 2017 19:58:34 +0000 (12:58 -0700)
committerMorgan Richomme <morgan.richomme@orange.com>
Wed, 8 Mar 2017 09:57:30 +0000 (09:57 +0000)
commit78949a3d610e2619c6f905502ea6798a20e535a8
tree587e9b9fadd04a9b7ba7c5783f787174b02763ce
parent486c2489fd9e44b10d7ffa63800a6c0710104645
Added support for scenario-based flavor creation.

As certain scenarios such as, DPDK, FDIO, and OVS use cases
require special 'hw:' settings to flavors, SNAPS-OO has just
implemented the ability to take in these configuration values
to apply to its integration tests. This change checks the
scenario and should be configuring the flavor metadata accordingly.

Also see SNAPS-38

Used this as an opportunity to refactor the SNAPS test classes as well...

JIRA: FUNCTEST-746

Change-Id: I63535776acde088a7461f602966a324b6207592d
Signed-off-by: spisarski <s.pisarski@cablelabs.com>
functest/core/pytest_suite_runner.py
functest/opnfv_tests/openstack/snaps/api_check.py
functest/opnfv_tests/openstack/snaps/connection_check.py
functest/opnfv_tests/openstack/snaps/health_check.py
functest/opnfv_tests/openstack/snaps/smoke.py
functest/opnfv_tests/openstack/snaps/snaps_test_runner.py [new file with mode: 0644]