openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/api
History
Eric Fried 1f546532c3 Create default network for more compute tests 
Chipping away at the referenced bug, this commit uses the
create_default_network class-level variable introduced via [1] to
trigger setup_credentials to create a default network for
a handful more test cases in which the problem was observed.

[1] Ia34fe3b41261de02918713c2a948e6c56554bf6f
Partial-Bug: #1844568

Change-Id: Ic38c74c245fddf29826e6ca0cc469f919076355e
 		2020-01-16 14:10:43 +00:00
..
compute Create default network for more compute tests 2020-01-16 14:10:43 +00:00
identity Merge ""test_project_get_equals_list" allows extra fields" 2019-09-03 20:40:07 +00:00
image Move upload/download image action to right place 2019-09-17 10:03:49 +08:00
network Merge "Remove test_agent_management tests" 2020-01-07 20:01:55 +00:00
object_storage docs: Fix incorrect docstrings in reStructuredText format 2018-11-21 19:06:43 -06:00
volume Merge "Enable volume backup tests" 2019-09-26 00:48:06 +00:00
README.rst Doc: fix markups, capitalization and add 2 REVIEWING advices 2017-07-11 20:26:32 +02:00
__init__.py Remove copyright from empty files 2014-01-14 03:02:04 +04:00

README.rst

Tempest Field Guide to API tests

What are these tests?

One of Tempest's prime function is to ensure that your OpenStack cloud works with the OpenStack API as documented. The current largest portion of Tempest code is devoted to test cases that do exactly this.

It's also important to test not only the expected positive path on APIs, but also to provide them with invalid data to ensure they fail in expected and documented ways. The latter type of tests is called negative tests in Tempest source code. Over the course of the OpenStack project Tempest has discovered many fundamental bugs by doing just this.

In order for some APIs to return meaningful results, there must be enough data in the system. This means these tests might start by spinning up a server, image, etc, then operating on it.

Why are these tests in Tempest?

This is one of the core missions for the Tempest project, and where it started. Many people use this bit of function in Tempest to ensure their clouds haven't broken the OpenStack API.

It could be argued that some of the negative testing could be done back in the projects themselves, and we might evolve there over time, but currently in the OpenStack gate this is a fundamentally important place to keep things.

Scope of these tests

API tests should always use the Tempest implementation of the OpenStack API, as we want to ensure that bugs aren't hidden by the official clients.

They should test specific API calls, and can build up complex state if it's needed for the API call to be meaningful.

They should send not only good data, but bad data at the API and look for error codes.

They should all be able to be run on their own, not depending on the state created by a previous test.