-
Notifications
You must be signed in to change notification settings - Fork 356
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
OpsRbac - specs for user add/edit #3916
Conversation
…success this was broken for a while before #3767, existing user could not be changed at all
on the one hand, these are tests written to check for specific regressions on the other, no other specs mention BZ numbers
@skateman I moved the methods to a helper, and removed the BZ numbers from the examples. => If anybody needs to know why a spec should not be failing, please read the relevant commit messages for BZ numbers. |
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.
Checked commits https://github.com/himdel/manageiq-ui-classic/compare/6f7f34ba7af4d14e6d08628fb6a77cdbe4a28ffa~...b6efd5e2afd9d3719312e5dc3276045099cb2850 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
Depends on ManageIQ/manageiq#17397Related to #3894, #3767, #3345 and #3714.
There's been too many problems recently with the code to add/edit a user in the UI - I've written specs for each of those problems (including a pending spec for the problem being fixed in #3894).
(Creating a new spec file, since
ops_controller/ops_rbac_spec.rb
is already too long and only deals with tenant, while user/group stuff is either untested or mixed together with the rest inops_controller_spec.rb
)Cc @lgalis , @ZitaNemeckova