openstack/tempest
Code Issues Proposed changes

Fix three accidentally formatted paragraphs

Browse Source 
Three paragraphs are misformated in the output due to
a leading space in a line. The leading space causes a
line break and the indent of the line.

Change-Id: I5c0d03a47a2ca305b2b077068df26fadccd72212
This commit is contained in:
Bruce R. Montague 2013-12-17 09:06:04 -08:00
parent dee1743ca6
commit 44a6a194ff
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
HACKING.rst
View File

@ -39,7 +39,7 @@ and ``finally`` block could replace the original exception,
when the additional operations leads to another exception. when the additional operations leads to another exception.
Just letting an exception to propagate, is not bad idea in a test case, Just letting an exception to propagate, is not bad idea in a test case,
at all. at all.
Try to avoid using any exception handling construct which can hide the errors Try to avoid using any exception handling construct which can hide the errors
origin. origin.
@ -53,10 +53,10 @@ exceptions and still ensure resources are correctly cleaned up if the
test fails part way through. test fails part way through.
Use the ``self.assert*`` methods provided by the unit test framework Use the ``self.assert*`` methods provided by the unit test framework
the signal failures early. the signal failures early.
Avoid using the ``self.fail`` alone, it's stack trace will signal Avoid using the ``self.fail`` alone, it's stack trace will signal
the ``self.fail`` line as the origin of the error. the ``self.fail`` line as the origin of the error.
Avoid constructing complex boolean expressions for assertion. Avoid constructing complex boolean expressions for assertion.
The ``self.assertTrue`` or ``self.assertFalse`` without a ``msg`` argument, The ``self.assertTrue`` or ``self.assertFalse`` without a ``msg`` argument,