Files
tempest/tempest/tests
Abhishek Bongale 8e2e854051 Fix tests for testtools 2.8.0 compatibility
From 2.8.0 testtools, testcase.TestSkipped has been removed we are
advice to replace with testcase.TestSkipped with unittest.skipTest

This PR trying to fix tests that are using TestSkipped by replacing it
with unittest.skipTest..

Closes-Bug: #2131281
Change-Id: I3bbdab71ec47f9c6ac99698aa1225239e7226706
Signed-off-by: Abhishek Bongale <abhishekbongale@outlook.com>
2025-12-03 17:33:28 +00:00
..
2021-02-24 12:45:22 +00:00
2024-01-31 09:00:16 +01:00
2024-11-14 23:39:15 +09: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)