airship
/
deckhand
Code Issues Proposed changes
deckhand/deckhand/tests/functional
History
Felipe Monteiro 11eeb69f44 integration tests: Add Barbican validation/assertions 
This patchset adds Barbican validation/assertions to integration
tests by querying the Barbican API server where appropriate
and validating that the expected data is returned in order
to sanity-check the integration scenarios further.

Change-Id: If5d30712b289f09ac9712ee205673be4150cda16
 		2018-07-22 16:32:57 +00:00
..
gabbits integration tests: Add Barbican validation/assertions 2018-07-22 16:32:57 +00:00
README.rst Clean up functional test directory and entrypoint script 2018-04-20 22:07:04 +01:00

README.rst

Functional Tests

Deckhand uses gabbi to drive its functional tests. The entry point for these tests is functional-tests.sh under tools directory.

Directory Test Layout

Tests are contained in intuitively named subdirectories nested under deckhand/tests/functional/gabbits. For example, layering tests are contained under the layering subdirectory. This pattern should be strictly followed.

Because gabbi does not support loading tests from subdirectories, logic is included in test_gabbi.py to:

  1. Create a temporary directory.
  2. Create a symlink between all the test files in the nested subdirectories and the temporary directory.

However, the test directory can still be modified:

  • New subdirectories under gabbits can be added.
  • New tests under any of those subdirectories can be added.
  • New resource files under gabits/resources can be added. This directory name should never be renamed.
  • All other subdirectories, test files, and resources may be renamed.