Add DEFAULT_TIMEOUT and TIMEOUT_SCALING_FACTOR3.7.0

The openstacksdk test suite sets a default value for OS_TEST_TIMEOUT to
enforce that no test in the suite should ever run long. It has to do
that by using the EnvironmentVariable fixture before running the super
setUp to get the value set before oslotest reads the environment
variable. Add a class variable that can be overridden to allow doing
that more cleanly.

Additionally, in the openstacksdk functional test suite, there is a
variable called "TIMEOUT_SCALING_FACTOR" that lets us mark that some of
the tests (I'm looking at you volume functional tests) naturally run a
bit longer than other tests in the suite. It's been invaluable for us
for a couple of ugly cases, so it seemed like we should upstream it into
oslotest.

Change-Id: I2ef5d0194185bf58c0945efb0725202e6d177e3f

1 files changed, 10 insertions, 0 deletions

diff --git a/releasenotes/notes/timeout-scaling-52741beadde528e5.yaml b/releasenotes/notes/timeout-scaling-52741beadde528e5.yaml
new file mode 100644
index 0000000..ad9f047
--- /dev/null
+++ b/releasenotes/notes/timeout-scaling-52741beadde528e5.yaml
@@ -0,0 +1,10 @@
+---
+features:
+  - |
+    New class variable, ``TIMEOUT_SCALING_FACTOR`` was added that allows
+    modifying a test class to have a longer timeout than other tests in the
+    suite without having to raise the default timeout for all tests.
+  - |
+    New class varable, ``DEFAULT_TIMEOUT`` was added that lets test suite
+    authors override the default value of ``OS_TEST_TIMEOUT`` at the
+    test suite level.