deckhand/deckhand/tests/functional
Felipe Monteiro b03a4522cb fix: Use schema instead of metadata.schema for replacement check
Recently added replacement check incorrectly uses metadata.schema
and metadata.name to key on the document -- but it should be schema
and metadata.name, the combination of which uniquely defines a
document.

Change-Id: I6cd1679ad41be38cb78d65ce2763e60f7da390d2
2018-10-31 15:02:28 -04:00
..
gabbits fix: Use schema instead of metadata.schema for replacement check 2018-10-31 15:02:28 -04: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.