airship
/
deckhand
Code Issues Proposed changes
deckhand/deckhand/tests/integration
History
Roman Gorshunov 5241d1d6ea Fix deckhand-integration-uwsgi-py35 tests 
During Gabbi tests server returns one of

  application/json
  application/json; charset=UTF-8

in a Content-Type HTTP header, depending on which test is being run.
This might be related to different pip/pip3 versions and dependencies
installed being used during standalone vs. containerized tests.

This patch allows for both returned header's values to be accepted as
valid as a remediate solution until versions of packages and pip/pip3
usage is unified.

Change-Id: Ifb8f2d68e3474946b3df154cb016cc18cfc95d23
 		2020-03-01 19:47:29 +01:00
..
gabbits Fix deckhand-integration-uwsgi-py35 tests 2020-03-01 19:47:29 +01:00
README.rst Add integration tests 2018-04-18 09:05:04 -04:00
__init__.py Add integration tests 2018-04-18 09:05:04 -04:00

README.rst

Integration Tests

What

These tests validate integration scenarios between Deckhand, Keystone and Barbican. These scenarios include validating Deckhand's secret lifecycle management as well as substitution of encrypted secrets, which are stored in Barbican and retrieved by Deckhand during document rendering.

How

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

The integration environment is deployed using OpenStack-Helm which uses Helm to orchestrate deployment of Keystone, Barbican and other pre-requisite services.

Usage

These tests can be executed via ./tools/integration-tests.sh <test-regex> from the command line, where <test-regex> is optional and if omitted all available tests are run. sudo permissions are required. It is recommended that these tests be executed inside a VM as a lot of data is pulled in (which requires thorough clean up) during the deployment phase.