The test's User utilities shouldn't require an admin property.

Registered by Tim Simpson

The Reddwarf tests have utility functions which find a user from a list of created users based on features of that user (this is to avoid hard coding specific users into the tests). They only require to know if the user is or is not an admin.

This is a bit silly as there are plenty of cases where it doesn't matter and the test code should be free to opt out of this.

I found while trying to run the tests against an environment where my Nova user worked only for the Nova MGMT api, but the test explicitly wanted a user who had access to the Nova services but was not an admin.

Blueprint information

Status:
Complete
Approver:
Tim Simpson
Priority:
Low
Drafter:
Tim Simpson
Direction:
Approved
Assignee:
Tim Simpson
Definition:
Discussion
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
None
Started by
Michael Basnight
Completed by
Michael Basnight

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/tests-should-not-require-admin-prop,n,z

Addressed by: https://review.openstack.org/31138
    Don't require an admin user if there isn't a need.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.