Use tempest plugin interface
Make use of the Tempest plugin interface instead of copying Neutron
files into Tempest. This will remove the burden to port Neutron
tests onto Tempest master recurrently.
It uses neutron/tests/tempest/ as new top folder for all Tempest
tests. It follows the model of Heat [1].
[1]: https://github.com/openstack/heat/tree/master/heat_integrationtests
Partially implements bp external-plugin-interface
Change-Id: Ia233aa162746845f6ae08a8157dcd242dcd58eab
diff --git a/neutron/tests/tempest/README.rst b/neutron/tests/tempest/README.rst
index 05ea998..d61e72c 100644
--- a/neutron/tests/tempest/README.rst
+++ b/neutron/tests/tempest/README.rst
@@ -3,8 +3,8 @@
The files under this path were copied from tempest as part of the move
of the api tests, and they will be removed as required over time to
-minimize the depedency on the tempest testing framework.
-While it exists, only neutron.tests.api and neutron.tests.retargetable should
-be importing files from this path. neutron.tests.tempest.config uses
+minimize the dependency on the tempest testing framework.
+While it exists, only neutron.tests.tempest.api and neutron.tests.retargetable
+should be importing files from this path. neutron.tests.tempest.config uses
the global cfg.CONF instance and importing it outside of the api tests
has the potential to break Neutron's use of cfg.CONF.