History

Paul Hinze 6fe2703665 Vendor all dependencies w/ Godep * Remove `make updatedeps` from Travis build. We'll follow up with more specific plans around dependency updating in subsequent PRs. * Update all `make` targets to set `GO15VENDOREXPERIMENT=1` and to filter out `/vendor/` from `./...` where appropriate. * Temporarily remove `vet` from the `make test` target until we can figure out how to get it to not vet `vendor/`. (Initial experimentation failed to yield the proper incantation.) Everything is pinned to current master, with the exception of: * Azure/azure-sdk-for-go which is pinned before the breaking change today * aws/aws-sdk-go which is pinned to the most recent tag The documentation still needs to be updated, which we can do in a follow up PR. The goal here is to unblock release.		2016-01-29 15:08:48 -06:00
..
openstack	Vendor all dependencies w/ Godep	2016-01-29 15:08:48 -06:00
rackspace	Vendor all dependencies w/ Godep	2016-01-29 15:08:48 -06:00
tools	Vendor all dependencies w/ Godep	2016-01-29 15:08:48 -06:00
README.md	Vendor all dependencies w/ Godep	2016-01-29 15:08:48 -06:00

README.md

Gophercloud Acceptance tests

The purpose of these acceptance tests is to validate that SDK features meet the requirements of a contract - to consumers, other parts of the library, and to a remote API.

Note: Because every test will be run against a real API endpoint, you may incur bandwidth and service charges for all the resource usage. These tests should remove their remote products automatically. However, there may be certain cases where this does not happen; always double-check to make sure you have no stragglers left behind.

Step 1. Set environment variables

A lot of tests rely on environment variables for configuration - so you will need to set them before running the suite. If you're testing against pure OpenStack APIs, you can download a file that contains all of these variables for you: just visit the project/access_and_security page in your control panel and click the "Download OpenStack RC File" button at the top right. For all other providers, you will need to set them manually.

Authentication

Name	Description
`OS_USERNAME`	Your API username
`OS_PASSWORD`	Your API password
`OS_AUTH_URL`	The identity URL you need to authenticate
`OS_TENANT_NAME`	Your API tenant name
`OS_TENANT_ID`	Your API tenant ID
`RS_USERNAME`	Your Rackspace username
`RS_API_KEY`	Your Rackspace API key

General

Name	Description
`OS_REGION_NAME`	The region you want your resources to reside in
`RS_REGION`	Rackspace region you want your resource to reside in

Compute

Name	Description
`OS_IMAGE_ID`	The ID of the image your want your server to be based on
`OS_FLAVOR_ID`	The ID of the flavor you want your server to be based on
`OS_FLAVOR_ID_RESIZE`	The ID of the flavor you want your server to be resized to
`RS_IMAGE_ID`	The ID of the image you want servers to be created with
`RS_FLAVOR_ID`	The ID of the flavor you want your server to be created with

2. Run the test suite

From the root directory, run:

./script/acceptancetest