Ken'ichi Ohmichi 899cf3918a Don't use Tempest internal methods ... All changed methods are clearly internal methods of Tempest, and the Tempest commit 64e6b4457c748f74bfb4fbf3860ab65b65ae9beb has removed the internal methods and now the gate issue happens. This patch makes this project to use better ones instead. Change-Id: I89283365517eea73d931f574e047b8af45e2b9f8 Related-Bug: #1667824		2017-02-24 16:10:47 -08:00
..
api	Tempest: Network tags clients, CRUD and Filter testing	2016-08-11 09:33:12 -07:00
dvs	Don't use Tempest internal methods	2017-02-24 16:10:47 -08:00
nsxv	Don't use Tempest internal methods	2017-02-24 16:10:47 -08:00
nsxv3	[Tempest]: Adding of Allowed address pair scenario cases.	2017-02-10 13:16:48 +00:00
scenario	Tempest: Remove deprecated tenant_id	2016-11-11 12:27:47 +00:00
suites	Tempest suite file for various versions of VIO testing	2016-08-23 19:14:16 -04:00
__init__.py	init release of vmware-nsx tempest tests in tempest external plugin	2016-01-21 10:02:00 -08:00
base.py	Tempest: Fixed error with nonexist module	2016-09-11 09:14:02 -07:00
test_vmware_nsx_tempest.py	Update gate logic	2016-07-12 09:05:22 -06:00