cinder/cinder/tests
Eric Harney b83c446e52 Tests: Make tests less random
Remove a bunch of uuid.uuid4() calls from tests, and use static UUIDs
instead.

We generally use static UUIDs to make test runs reproducible and to make
it easier to track odd failures that repeat in the gate.

Readability of tests is also improved by using meaningful names like
VOLUME_ID or SNAPSHOT_ID rather than just uuid4().

So, do more of that.

Some care has to be taken in test classes that create lots of volumes,
such as BackupBaseDriverTestCase, because random UUIDs were previously
allowing volumes used by different tests to not collide with each other.
More static IDs have been added to account for this.

Change-Id: I372d27367b730f4606bc0ea84a9b322d45d1cbbe
2020-05-08 11:22:02 -04:00
..
compliance Use assertEqual/Less/Greater/In/IsNone 2016-07-04 17:58:16 +02:00
functional Move unit test code under tests/unit/ 2020-04-30 18:13:54 -04:00
hacking Add hacking check for 3rd party mock 2020-04-09 15:21:12 -05:00
unit Tests: Make tests less random 2020-05-08 11:22:02 -04:00
README.rst Update the documentation link 2017-08-26 06:52:48 -07:00
__init__.py
fake_driver.py Rename volume/utils.py to volume/volume_utils.py 2019-09-09 15:00:07 -04:00
fixtures.py Implement privsep boilerplate in cinder. 2018-06-06 09:42:54 +08:00

README.rst

IMPORTANT DEFINITION OF TESTS IN CINDER

Cinder has a number of different test types, PLEASE be sure to refer to the Cinder Testing Docs to familiarize yourself with the various options before creating any new tests.

Please check Cinder-Testing.