From 0a83c71252897e214eb58cec2c00a6b1f2905e99 Mon Sep 17 00:00:00 2001 From: David Rabel Date: Thu, 24 May 2018 08:45:26 +0200 Subject: [PATCH] Fix indentation in README.rst Old indentation was wrongly interpreted as quotation. Change-Id: I358bceda64ee671e5e07d74ec66a7658ac382dec --- tempest/README.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/tempest/README.rst b/tempest/README.rst index 62821de654..a5f4a923ed 100644 --- a/tempest/README.rst +++ b/tempest/README.rst @@ -12,12 +12,12 @@ As such Tempest tests come in many flavors, each with their own rules and guidelines. Below is the overview of the Tempest respository structure to make this clear. - .. code-block:: console +.. code-block:: console - tempest/ - api/ - API tests - scenario/ - complex scenario tests - tests/ - unit tests for Tempest internals + tempest/ + api/ - API tests + scenario/ - complex scenario tests + tests/ - unit tests for Tempest internals Each of these directories contains different types of tests. What belongs in each directory, the rules and examples for good tests, are