<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/openstack/python-keystoneclient.git/keystoneclient/fixture/exception.py, branch queens-em</title>
<subtitle>opendev.org: openstack/python-keystoneclient.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/python-keystoneclient.git/'/>
<entry>
<title>map fixtures to keystoneauth</title>
<updated>2016-05-22T06:24:40+00:00</updated>
<author>
<name>Steve Martinelli</name>
<email>stevemar@ca.ibm.com</email>
</author>
<published>2016-03-10T06:36:32+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/python-keystoneclient.git/commit/?id=e26e79e68af4105075b537346c546daa0d01616f'/>
<id>e26e79e68af4105075b537346c546daa0d01616f</id>
<content type='text'>
point to the latest fixtures in keystoneauth so we do not need to
update code in two spots.

Change-Id: I1e9ffdafd4dc06b84bc643e570dbea0132b47540
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
point to the latest fixtures in keystoneauth so we do not need to
update code in two spots.

Change-Id: I1e9ffdafd4dc06b84bc643e570dbea0132b47540
</pre>
</div>
</content>
</entry>
<entry>
<title>Create a test token generator and use it</title>
<updated>2014-04-03T01:20:33+00:00</updated>
<author>
<name>Jamie Lennox</name>
<email>jamielennox@redhat.com</email>
</author>
<published>2014-03-07T03:20:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/python-keystoneclient.git/commit/?id=d69461b18fcd05fdce63e98634cd6e7f102ff091'/>
<id>d69461b18fcd05fdce63e98634cd6e7f102ff091</id>
<content type='text'>
All the clients are currently storing samples of keystone tokens so that
they can use them in testing. This is bad as they are often out of date
or contain data that they shouldn't.

Create a V2 Token generator and make use of that for generating tokens
within our tests.

Change-Id: I72928692142c967d13391752ba57b3bdf7c1feab
blueprint: share-tokens
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
All the clients are currently storing samples of keystone tokens so that
they can use them in testing. This is bad as they are often out of date
or contain data that they shouldn't.

Create a V2 Token generator and make use of that for generating tokens
within our tests.

Change-Id: I72928692142c967d13391752ba57b3bdf7c1feab
blueprint: share-tokens
</pre>
</div>
</content>
</entry>
</feed>
