deckhand/deckhand/tests/functional
Felipe Monteiro 29894ee854 Move to stestr for functional/integration tests
This moves to stestr for functional/integration tests to
align with preferred OpenStack test runner and also because
py.test is causing issues here: [0].

[0] http://logs.openstack.org/45/573045/8/check/airship-deckhand-integration-uwsgi-py35/60bd7ae/job-output.txt.gz#_2018-06-22_03_00_51_267408

Change-Id: I701c71aef2a122b8f1fc64285cb799f71cfe520f
2018-07-21 15:32:26 -04:00
..
gabbits Move to stestr for functional/integration tests 2018-07-21 15:32:26 -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.