openstack/tempest
Code Issues Proposed changes

Merge "fix: Re-clarify unit test REVIEWING documentation"

Browse Source
This commit is contained in:
Zuul
2018-09-26 20:52:00 +00:00
committed by Gerrit Code Review
parent 9a95eb84ea a7365ae219
commit fd236826dc
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
REVIEWING.rst
View File

@@ -36,8 +36,11 @@ Unit Tests
For any change that adds new functionality to either common functionality or an
out-of-band tool unit tests are required. This is to ensure we don't introduce
future regressions and to test conditions which we may not hit in the gate runs.
Tests, and service clients aren't required to have unit tests since they should
be self verifying by running them in the gate.
API and scenario tests aren't required to have unit tests since they should
be self-verifying by running them in the gate. All service clients, on the
other hand, `must have`_ unit tests, as they belong to ``tempest/lib``.
.. _must have: https://docs.openstack.org/tempest/latest/library.html#testing
API Stability