Problem/Motivation
Add test scenario to check if the user does not have access to view/edit resources when they do not have permission
[Method]
- After creating all the resources, remove all the permissions or log-in with a user does not have permission to the resources at all.
[What to check]
- Check if the user can see the button to add a resource in each tab of resources
- Go to the the link of [ cloud_context/resource_name/edit/ ], and make sure the user will get a 403 HTTP response
Issue fork cloud-3268673
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3268673-add-a-bdd
compare
- 3268673-2
changes, plain diff MR !746
Comments
Comment #3
TamakiFujino commentedComment #4
TamakiFujino commentedComment #5
TamakiFujino commentedComment #7
yas@tamakifujino
Thank you for adding the test case. It looks good to me.
@kumikoono
What do you think? Thanks
Comment #8
kumikoono commentedThis is non-authorized user's test, namely semi-normal test type. So, the file name should be
AWS-ATDD-01-xx. ( However, we need to add some order control. )Moreover, it's better to break into two feature files:
Both should run and pass anytime, but it's meaningful when the 2nd file run after some resources are created.
Thus, can you create
AWS-ATDD-00-21-NonAuthorizedUserAccess.featureandAWS-ATDD-00-22-NonAuthorizedUserCheckResources.featurefor them?Comment #9
TamakiFujino commentedComment #10
TamakiFujino commentedComment #11
kumikoono commented@tamakifujino Thanks for the update. I think the filenames should switch each other. Other than that, they look good to me.
Comment #12
kumikoono commentedLooks good to me. Thanks!
Comment #13
yas@tamakifujino
Thank you for the change. I'll merge the patch to
4.xand5.x, and close this issue as Fixed.Comment #16
yas