-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
split valid_user_data and valid_new_user fixtures by roles #124
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fbalak At 1st sight this looks good, but could you link to the definition of Tendrl user types? Is this specified anywhere?
new fixtures: valid_new_normal_user valid_normal_user_data valid_new_admin_user valid_admin_user_data Roles are defined in: https://redhat.invisionapp.com/share/KNB25OEQT#/screens/226063796 Change of role names: https://github.com/Tendrl/specifications/pull/237/files
@mbukatov I have linked it in commit message. |
@fbalak Thanks! Do you think it would make sense to add this information into comment or docstring of the fixture? |
@mbukatov I wouldn't link design documents directly into docstring but I updated the docstring based on: |
@mbukatov Added reference links to docstring. |
This needs to be reworked. |
new fixtures:
valid_new_normal_user
valid_normal_user_data
valid_new_admin_user
valid_admin_user_data
If this PR will be merged I will create an issue that reminds us that there should be created separate test case for admin roles (or maybe create one more fixture to yield users of all roles...).
Roles are defined in:
https://redhat.invisionapp.com/share/KNB25OEQT#/screens/226063796
Change of role names:
https://github.com/Tendrl/specifications/pull/237/files