Files
tempest/tempest/tests
Rao Adnan KhanandGhanshyam Mann ac1aaf6624 Add client for assisted volume snapshots API.
This will invoke post and delete calls on os-assisted-volume-snapshots
endpoint.

Closes-bug: #1668407

Co-Authored-By: Ghanshyam Mann <gmann@ghanshyammann.com>

Change-Id: I81e8fd9f89ec1cb00fc0116c31f9c0559406164
2021-03-23 17:04:50 -05:00
..
2021-02-24 12:45:22 +00:00
2021-02-19 20:02:01 +00:00
2020-04-04 10:33:23 +02:00
2021-02-24 12:45:22 +00:00
2021-02-24 12:45:22 +00:00

Tempest Field Guide to Unit tests

What are these tests?

Unit tests are the self checks for Tempest. They provide functional verification and regression checking for the internal components of Tempest. They should be used to just verify that the individual pieces of Tempest are working as expected. They should not require an external service to be running and should be able to run solely from the Tempest tree.

Why are these tests in Tempest?

These tests exist to make sure that the mechanisms that we use inside of Tempest are valid and remain functional. They are only here for self validation of Tempest.

Scope of these tests

Unit tests should not require an external service to be running or any extra configuration to run. Any state that is required for a test should either be mocked out or created in a temporary test directory. (see test_wrappers.py for an example of using a temporary test directory)