integration

Integration Testing

⚠️ WARNING

The integration tests are going to communicate with and modify a real OneView appliance.

The tests do their best cleanup after themselves, but know what they do before running them!

Setup

First, there's some setup you'll need to do. Do EITHER of the following:

Option 1: Use default config file locations

Copy the one_view_config.json.example, one_view_secrets.json.example, one_view_synergy_config.json.example and one_view_synergy_secrets.json.example files into the same directory (spec/integration) and drop the .example part of the filename on the new copies. You should now have the following files:

spec/integration/one_view_config.json # Tests for APIs v200, v300, v500 v600 and v800 C7000
spec/integration/one_view_secrets.json # Tests for APIs v200, v300, v500 v600 and v800 C7000
spec/integration/one_view_synergy_config.json # Tests for APIs v300, v500 v600 and v800 Synergy
spec/integration/one_view_synergy_secrets.json # Tests for APIs v300, v500 v600 and v800 Synergy

Option 2: Use environment variables to specify config file locations:**

1. Copy the one_view_config.json.example, one_view_secrets.json.example, one_view_synergy_config.json.example and one_view_synergy_secrets.json.example files to a secure location outside this repo. When you do so, drop the .example part of the filename.

   • one_view_config.json.example: Tests for APIs v200, v300, v500 v600 and v800 C7000
   • one_view_secrets.json.example: Tests for APIs v200, v300, v500 v600 and v800 C7000
   • one_view_config.json.example: Tests for APIs v300, v500 v600 and v800 Synergy
   • one_view_secrets.json.example: Tests for APIs v300, v500 v600 and v800 Synergy

2. Then set the following environment variables with the paths to the files you just created:

   export ONEVIEWSDK_INTEGRATION_CONFIG='/path/to/one_view_config.json'
   export ONEVIEWSDK_INTEGRATION_SECRETS='/path/to/one_view_secrets.json'
   export ONEVIEWSDK_INTEGRATION_CONFIG_SYNERGY='/path/to/one_view_synergy_config.json'
   export ONEVIEWSDK_INTEGRATION_SECRETS_SYNERGY='/path/to/one_view_synergy_secrets.json'

These config files get loaded and create the following global variables:

• $secrets: Credentials for connecting to new resources
• $config: Config for connecting to OneView appliance
• $client_120: Client object pinned to API v120
• $client: Client object pinned to API v200
• $client_300: Client object pinned to API v300 C7000
• $client_300_synergy: Client object pinned to API v300 Synergy
• $client_500: Client object pinned to API v500 C7000
• $client_500_synergy: Client object pinned to API v500 Synergy
• $client_600: Client object pinned to API v600 C7000
• $client_600_synergy: Client object pinned to API v600 Synergy
• $client_800: Client object pinned to API v800 C7000
• $client_800_synergy: Client object pinned to API v800 Synergy

Setup for Image Streamer

First, there's some setup you'll need to do. Do EITHER of the following:

Option 1: Use default config file locations

Copy the one_view_synergy_config.json.example and i3s_config.json.example files into the same directory (spec/integration) and drop the .example part of the filename on the new copies. You should now have the following files:

spec/integration/one_view_synergy_config.json
spec/integration/i3s_config.json # Tests for APIs v300. v500, v600 Image Streamer

Option 2: Use environment variables to specify config file locations:**

1. Copy the one_view_synergy_config.json.example and i3s_config.json.example files to a secure location outside this repo. When you do so, drop the .example part of the filename.

   • one_view_synergy_config.json.example:
   • i3s_config.json.example: Tests for APIs v300, v500, v600 Image Streamer

2. Then set the following environment variables with the paths to the files you just created:

   export ONEVIEWSDK_INTEGRATION_CONFIG_SYNERGY='/path/to/one_view_synergy_config.json'
   export I3S_INTEGRATION_CONFIG='/path/to/i3s_config.json'

These config files get loaded and create the global variables:

• $client_i3s_300: Client object pinned to API v300 Image Streamer
• $client_i3s_500: Client object pinned to API v500 Image Streamer
• $client_i3s_600: Client object pinned to API v600 Image Streamer

Running the tests

The following command must run in your Ruby SDK root directory:

Run $ rake -T to show all the available rake tasks.

Then run any number of integration tests:

$ rake integration
$ rake integration:path[path]  # e.g. integration:path[spec/integration/resource/api200/connection_template]

$ rake integration:only[action,type,api_ver,variant] # e.g. integration:only[create,volume,300,c7000]
$ rake integration:only[action]                      # actions: create, update, delete
$ rake integration:only[,type]                       # e.g. integration:only[,volume_template]
$ rake integration:only[,,api_ver]                   # e.g. integration:only[,,300]
$ rake integration:only[,,,variant]                  # e.g. integration:only[,,,synergy]
$ rake integration:only[,,api_ver,variant]           # e.g. integration:only[,,300,c7000]

# Tests for Image Streamer
$ rake integration_i3s
$ rake integration_i3s:path[path]   # e.g. test:i3s:path[spec/integration/image-streamer/api300/os_volume]

$ rake integration_i3s:only[action,type,api_ver] # e.g. integration_i3s:only[create,build_plan,300]
$ rake integration_i3s:only[action]              # actions: create, update, delete
$ rake integration_i3s:only[,type]               # e.g. integration_i3s:only[,build_plan]
$ rake integration_i3s:only[,,api_ver]           # e.g. integration_i3s:only[,,300]

Note: Set the PRINT_METADATA_ONLY environment variable to print the order of the tests only (without actually running any tests)