8 Commits

Author SHA1 Message Date
Alistair Coles
17fda64f22 Fix swiftclient func tests to run using both auth versions
The rationale for this change is the same as for merged change
to swift func tests job [1].

The swiftclient functional test job was changed to run
tox -e func as sudo [2]. The job first runs functional tests
against keystone, then repeats the tests against tempauth.
The second part of the job requires SWIFT_TEST_CONFIG_FILE
env var to be set to cause the tests to run against tempauth.
The introduction of sudo in [2] causes this env var to be lost,
so the tests run against keystoneauth again.

[1] change id Ibea153e94e7919b5422a344d365cee3106efb2fe
[2] change id Ifc3e862b0fe86928c3943a41f07cd086d6ace6fe

Change-Id: Ieea3efbd6526edb8038b677a2e2278107acfe211
2015-03-03 15:35:46 +00:00
Alistair Coles
73b96a02f7 Fix swift func tests to run using both auth versions
The swift functional test job was changed to run
tox -e func as sudo [1]. The job first runs functional tests
against keystone, then repeats the tests against tempauth.
The second part of the job requires SWIFT_TEST_CONFIG_FILE
env var to be set to cause the tests to run against tempauth.
The introduction of sudo in [1] causes this env var to be lost,
so the tests run against keystoneauth again.

A tell-tale is that the second run of the functional tests should
output "SKIPPING FUNCTIONAL TESTS SPECIFIC TO AUTH VERSION 3" before
the first line of test results. This has been missing since [1] was
merged.

[1] change id Ifc3e862b0fe86928c3943a41f07cd086d6ace6fe

Change-Id: Ibea153e94e7919b5422a344d365cee3106efb2fe
2015-02-24 12:37:24 +00:00
Sean Dague
57ecb487a1 add sudo permissions to swift functional jobs
the swift functional jobs need to run as the stack user if they are
going to build the .tox directory in the appropriate tree.

Change-Id: Ifc3e862b0fe86928c3943a41f07cd086d6ace6fe
2015-02-18 11:15:52 -05:00
Sean Dague
d19009b495 make swiftclient functional job use swiftclient from git
This fix allows the swiftclient functional job to use swiftclient from
git, instead of only from pypi, which is needed for testing commits to
the client.

Change-Id: Ib239e55993b6cdc462db7b9854061b7352bbdccd
2015-02-17 22:09:17 +00:00
Sean Dague
091a6c7e9c have swift functional tests use tox
the swift functional tests should use tox targets when run in the gate
so that their test requirements can be specified in the swift project
itself, instead of being bound to what might be available in the base
image.

Depends-On: I730f1bb530215ba7c30bf32a1c3bbc16edd5c217

Change-Id: Ida1ee74162cb3b0f575364f9e4bf7742ccd9a794
2015-02-17 22:09:08 +00:00
Christian Schwede
98f1937ce2 Install test-requirements for swiftclient functional tests
The functional test for python-swiftclient currently fails all the time because
an required package for testing (testrepository) is missing.

swift itself uses nosetest to start functional tests, but python-swiftclient
uses testr and thus requires the package testrepository to be installed.

This patch simply installs all requirements for the tests. I was able to
reproduce this error localy using a fresh virtualenv environment, and this
patch fixed it for me.

Change-Id: I5417f74d324b1915155e321c3a87138069aa35fa
2015-01-26 11:04:22 +01:00
Christian Schwede
0871697b30 Enable functional tests for python-swiftclient
This patch starts a new devstack VM and runs functional tests for
python-swiftclient on it.

Change-Id: Idf1a573f750480e03a53db7f8d5a0682707599f6
2014-09-30 16:52:07 +02:00
Anita Kuno
1d21cd635f Reorganizes project-config
This repo was created from filter branching the openstack-infra/
config repo. This process brought a lot of cruft with it in the
form of directories that we no longer need. This patch removes
that cruft so we begin with a tidier repo.

Change-Id: Ibffad1b11c0c5f84eedfb0365369f60c4961a0f3
2014-09-25 11:41:04 -04:00