The script will take a directory or url containing log files.
For now all non-whitelisted errors will be dumped to the console but
the script will always return success. Once we are convinced it is reliable
enough we can change it to fail on non-whitelisted errors.
Partially implements blueprint fail-gate-on-log-errors
Change-Id: I30b0eee1055f47aaad7984d886c739ccf5aa6186
This commit adds a new section to HACKING.rst to outline the
guidelines for adding negative tests to tempest.
Change-Id: Ieb3fc3670bb9229c6791e5c8c0a7ac4fbde03c4d
This commit updates lockutils from oslo incubator which adds a
LockFixture class. This also converts the tempest LockFixture to wrap
the fixture from oslo.
Change-Id: I4f5007109fa6ceff868c23d55d9962f9d703bb1f
There have been some issues with performance around security groups in
the past. Lets make sure they don't exist.
We gate on test_large_ops as part of gate-tempest-devstack-vm-large-ops
Change-Id: Ib655deab9fc12df969b47552d7d8edc999c0d06a
The scenario base class has code to properly clean up servers and
wait until they are fully deleted. Use this instead of custom cleanup
which doesn't wait for delete to complete.
Change-Id: Ic9fe5ea0d267116d5bc78f50d1945602e5247d6a
make a seperate file test_users_negative.py and move exist negative tests
over to it,also add some negative tests to it
- test_create_user_with_enabled_non_bool
- test_create_user_with_enabled
- create_user
- test_update_user_for_non_existant_user
- test_update_user_request_without_a_token
- test_update_user_by_unauthorized_user
- test_delete_user_request_without_a_token
Change-Id: I5a87d72ecb94046809faf0ce14b1af347c2e4dcc
tempest/config.py has many simliar tiny functions for register_*_opts.
We should remove the code duplication to providing a common function.
Change-Id: Ie8facc21a2d8a1e27687b1182a3db9f98bc1a05e
Closes-Bug: #1236498
Sometimes the nightly stress test run fails. This will catch all
exceptions in run_stress.py and log them.
Change-Id: Ib6abd2c157df3988ccae1c6c8f703ec0ed24ff00
Fixes-bug: 1234580
Change I8519cba1fcf6ff39d69839783d07359544509db5 was supposed to make
the setup for test_list_servers_negative.py handle the case that tempest
is being ran without tenant isolation, but it doesn't fix the entire
problem because it's only checking if the MULTI_USER global is False.
The MULTI_USER global is only False if allow_tenant_isolation=False and
user1 == user2. So if you're running tempest without tenant isolation
but you do have two separate users/tenants for running the tests, then
the setup can still fail.
This patch fixes the problem by always doing the cleanup if
allow_tenant_isolation=False regardless of what MULTI_USER is set to.
Closes-Bug: #1234370
Change-Id: I821e200d07c11ba04d8be788095b7648de1d820b
If we use skip_because decorator, the below error occurs.
_StringException: ImportError: Failed to import test module:...
And, all tests of the class having the skip_because decorator are not
tested.
This commit fixes it.
Change-Id: I98e51d3bfd8b13dc3ef462eb92b170295f5f142e
Closes-Bug: #1236220
The setup method of test_volumes_actions generates a random name for the
instance and volume it uses for the tests but the names don't include
the test class so if they don't get cleaned up it's hard to debug where
they came from. This patch simply adds the class name to the
instance/volume name generation.
Closes-Bug: #1235411
Change-Id: If457e73c11f08fd57ee77a85208de84fc39eda8c
The test_list_server_filters test class was doing a lot of
setup/teardown work that is now handled in the parent class. We still
have to explicitly set the name since some tests use it for filtering
but otherwise we can rely on the parent class to do most of the heavy
lifting here.
This change makes it so that the instances have a name based on the test
class rather than just a random integer which is hard to use for
debugging leaked instances.
This change also removes the get call from setup and moves it into the
test cases that actually need to use it (which are currently being
skipped anyway).
Closes-Bug: 1235411
Change-Id: I66813c900059dd4232de645c225032e58e9aecde
When unseting a nonexistent key, an exception should be raised.
when settting flavor extra specs, key is arbitrary, so
'set_nonexistent_key' does not make sense
Change-Id: I1b94a8b9524ed67dfc3fb1afd51442b740873638
