6 Commits

Author SHA1 Message Date
zhufl
0419088f9d Replace the usage of 'os' with 'os_primary'
Read-only property 'os' has moved to 'os_primary' in version 'Pike'
and will be removed in version 'Queens', so this is to replace
the usage of 'os' with 'os_primary'.

Change-Id: I9f7c13da05a8c4a63529c11aa6213a7269abee6d
2017-05-23 10:45:48 +08:00
Jordan Pittier
8160d31e58 test.py: stop using aliases for creds manager
It could be confusing to new comers that the variables
cls.os and cls.os_primary or cls.alt_manager and cls.os_alt
actually are aliases. Besides we are not consistent in their usage.

This patch normalizes the usage around os_admin, os_primary and
os_alt. We keep the old aliases for compatibility but we should not
use them anymore.

This fix a long standing TODO item.

Change-Id: I5f7164f7a7ec5d4380ca22885000caa0183a0bf7
2017-04-26 10:34:56 +02:00
zhufl
2e644e6519 Fix the position of the dots in write_tests.rst
This is to move the dots to the end of the sentences.

Change-Id: I2f6906efc8f63f39737c73301e7239b1c7e18ea8
2017-04-21 14:14:54 +08:00
Matthew Treinish
19b7ba4229
Add write tests docs for using client managers and credentials
This commit adds documentation on how to interact with clients, client
managers, and credentials objects. These are critical pieces of
information for anyone writing tempest tests, so making sure the guide
includes this information is equally important.

Change-Id: I89e2c137068eea8aeaff0561fe078eccd3a23f0e
2017-04-17 10:08:31 -04:00
Matthew Treinish
8f28d1fff4
Fix heading levels in write_tests doc
This commit fixes the top level header for the write_tests doc.
Previously, the doc title was set as the same as the section. This
caused things like table of contents to confuse the hierarchy of the
sections in the docs. This commit fixes that by setting the doc title
to be a higher lever in the hierarchy.

Change-Id: I2ecb110c766a71e1dc2d9e663ca38ece76dc327d
2017-04-08 21:35:41 -04:00
Matthew Treinish
e8ab5f9b08
Add tempest test writing guide
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
2017-04-03 11:53:35 -04:00