Thorough replacement of git.openstack.org and review.openstack.org URLs
with their opendev.org counterparts.
Change-Id: I88e894db7b854d32593c770f5aa9b8a91fad7866
This patchset fixes typos (capitalization mistakes,
grammar mistakes) found in the documentation pages.
Change-Id: If500aeab1af7dd8b56d63cbc481ee501216df161
In "While there are no hard and fast rules for the structure a plugin"
a preposition is missing between "structure" and "a plugin", this is
to fix it.
Change-Id: Ib22f614dece35d2ed79fa660027e50840e77d7bb
test.py and clients.py now only depend on stable
interfaces and can be marked stable for plugins.
Previous patches added unit tests and docstrings
for most methods.
Change-Id: I22cb1a7744d2310f9b70769e136803a607217ceb
Add unit tests for credentials_factory and mark it stable for
plugins. This is part of the work to make tempest/test.py stable
for plugins.
Change-Id: I99414cb2704ce5469fcb66406b6905e2d1871dba
This commit is the start of a new doc guide for helping people figure
out how to write good tempest tests. This is just a starting point for
the document and doesn't cover every aspect of writing a test case in
tempest. Right now it just covers the setupClass phase for writing
TestCases. It will be expanded upon in future commits to give a complete
guide to writing tests in Tempest.
Change-Id: Ie0db2079163f536ae72668c8fc9129ae4c6389e2
Migrate the service_clients module to tempest.lib.services.clients.
Migrate related unit tests as well.
The clients module atm imports plugin.py from Tempest which is not
allowed via hacking to avoid cirtular dependencies.
If there is no way around this, I will have to remove the self
registration of the service clients from plugins, and ask the
plugins to do the registration themselves - which is a pity. Ideas?
Change-Id: I40e3478f69af62a7cdc14fa65ed21dcfbbe10e72
Plugin authors can have a hard time determining which APIs are acceptable
to use, and which are not. We should provide an explicit list on the
plugin interface doc page.
Change-Id: I475a8ccc568077a4824fda0ddc20606a0ffabbc7
This commit adds a subsection to the creating a plugin section in the
plugin doc that tries to strongly advocate creating a separate python
package for tempest plugins for various reasons. This will hopefully
steer potential plugin authors towards doing this.
Change-Id: Id3c06381c0d8e79f59e50486a3c10b12bb977c51
Currently, in Usage, there is no installation procedure of cookiecutter.
This patch set adds installation procedure of cookiecutter to README.rst
Change-Id: Ief3a1fdab945c1df834b219fadadf8d2b5d824a4
Since we have a official cookiecutter project we should
rely on it in the documentation. All titles are moved a bit
since only the usage of the cookiecutter and the entry point
is needed to create a working test project. All other information
is just additional and not mandatory for plugin creation.
Change-Id: Ia04d2ea747f19d7b1d272bd7664ff05f61c7c88c
This commit adds a subsubsection to the plugin interface docs to
elaborate a bit on how to deal with configuration options. Previously,
how to use them in a plugin was implied, but nothing was explicitly
stated. This corrects that to make it clear on how to deal with
configuration.
Change-Id: Id3afc9657c5419cfba61acb3c84ccfea104d1b20
This commit starts the docs section on creating and using tempest
plugins. It describes how to create a plugin class, an entrypoint, and
a recommended dir structure. As well notes how to use tempest and
tempest-lib in creating a plugin. It'll likely be expanded in the
future as the plugin interface evolves.
Partially Implements bp external-plugin-interface
Change-Id: If2e0c47d0a719d869a3301ddbca07495c81cc498