4870aee2a1
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_create_vlan_backed_gvt_with_incorrect_network_type_manual [0.315791s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_create_vlan_backed_gvt_with_incorrect_physical_network_id [0.619839s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_create_vlan_enabled_network_vlan40to1000and_update_subnet [21.580483s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_create_vlan_enabled_network_vlan40to1000and_updateqos [27.156031s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_create_vlan_enabled_network_vlan_40to1000with_disabled_dhcp [18.911594s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_delete_vlan_enabled_network_with_enabled_gvt_manual [3.854728s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_delete_vxlan_enabled_network_manual [2.748262s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_read_vlan_enabled_network_with_enabled_gvt [3.305594s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_read_vxlan_enabled_network [2.604374s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_update_subnet_vlan_enabled_network_with_enabled_gvt [4.314844s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_update_subnet_vxlan_enabled_network_with_enabled_gvt [3.468739s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_update_vlan_enabled_network_40to1000with_port_sec_dis [21.722404s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_update_with_port_security_vlan_enabled_network_with_gvt [5.927418s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_update_with_port_security_vxlan_enabled_network_with_gvt [3.736936s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_update_with_qos_vlan_enabled_network_with_enabled_gvt [7.531114s] ... ok
{0} vmware_nsx_tempest_plugin.tests.scenario.test_gvt.GuestVlanTaggingTests.test_update_with_qos_vxlan_enabled_network_with_enabled_gvt [6.458085s] ... ok
Change-Id: Iec639691662f8b72ad7ba3b92e15dce1002aec03
|
||
|---|---|---|
| doc | ||
| releasenotes | ||
| vmware_nsx_tempest_plugin | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .testr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| lower-constraints.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Welcome!
vmware-nsx-tempest-plugin
Tempest plugin vmware-nsx-tempest-plugin
This repo hosts vmware-nsx's functional api and scenario tests.
vmware-nsx is Vmware plugin for neutron. This repo is tempest plugin to test vmware-nsx at function level. All vmware-nsx-tempest-plugin tests are in "master" branch. Some of the tests are designed based on N-S traffic. Intstall thsi repo on external VM to run entire test suite.
- Free software: Apache license
- Launchpad: https://launchpad.net/vmware-nsx-tempest-plugin
- Source: http://git.openstack.org/cgit/openstack/vmware-nsx-tempest-plugin
- Bugs: http://bugs.launchpad.net/vmware-nsx-tempest-plugin
Features:
- API tests
- Scenario tests
Overview:
Installation:
On your own development folder, for example /opt/stack/, install your own tempest development env at /opt/stack/tempest/:
$ cd /opt/stack $ git clone https://github.com/openstack/tempestInstall virtualenv with the following command:
$ cd /opt/stack/tempest $ ./run_tempest.sh -u not_exist_testsInstall vmware-nsx-tempest-plugin master branch at /opt/stack:
$ cd /opt/stack $ git clone https://github.com/openstack/vmware-nsx-tempest-plugin.gitInstall vmware-nsx-tempest-plugin in your tempest development environment:
$ cd /opt/stack $ sudo pip install -e vmware-nsx-tempest-pluginRun command:
$ pip show vmware-nsx-tempest-pluginYou should observe the following statements:
Location: /opt/stack/vmware-nsx-tempest-pluginValidate installed vmware_nsx_tempest_plugin successfully do:
$ cd /opt/stack/vmware-nsx-tempest-plugin $ ostestr -l vmware_nsx_tempest_plugin $ ostestr vmware_nsx_tempest_plugin.tests.nsxv3.scenario.test_mdproxy.TestMDProxy.test_mdproxy_ping $ python -m testtools.run vmware_nsx_tempest.tests.nsxv3.scenario.test_mdproxy.TestMDProxy.test_mdproxy_ping
Your installation failed, if no tests are shown.
Execution:
vmware-nsx-tempest tests are tempest tests, you need to run from tempest directory. For example, to run only l2-gateway tests:
$ cd /opt/stack/tempest
$ ostestr vmware_nsx_tempest_plugin.*test_l2_gateway
$ ostestr vmware_nsx_tempest_plugin.tests.nsxv.api.test_l2_gateway_connection.L2GatewayConnectionTest.test_csuld_single_device_interface_vlanTechNote on vmware-nsx-tempest-plugin:
vmware-nsx-tempest-plugin is a plugin to tempest, not neutron, nor vmware-nsx. It is defined by tempest.test_plugins.
Modules within vmware-nsx-tempest can not see resources defined by vmware-nsx. Commands like following will not work, unless vmware-nsx is installed in your tempest environment:
import vmware_nsx.shell.admin.plugins.common.utils as admin_utils