-
Notifications
You must be signed in to change notification settings - Fork 197
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
[tests-only][full-ci] added test to send share invitation to non-existing group #8175
Conversation
770b5b6
to
898d5ad
Compare
| Viewer | file | /textfile1.txt | | ||
| File Editor | file | /textfile1.txt | | ||
| Co Owner | file | /textfile1.txt | | ||
| Manager | file | /textfile1.txt | | ||
| Viewer | folder | FolderToShare | | ||
| Editor | folder | FolderToShare | | ||
| Co Owner | folder | FolderToShare | | ||
| Uploader | folder | FolderToShare | | ||
| Manager | folder | FolderToShare | |
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.
all role should not be allowed to file resource see issue #8131
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.
Currently every role can be assigned on the file, and this same example table is being used in every other Scenario. What should we do about it? Should we do it as it is or should we wait for some fixes?
cc @amrita-shrestha @saw-jan
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.
I really don't know what roles should be permitted while sharing a file/folder. If it is known then we can make another PR for removing not permitted roles and add some coverage for trying to share with not permitted roles. Then block that PR until the fix arrives
But I don't think we need to block this one.
tests/acceptance/features/apiSharingNg/shareInvitations.feature
Outdated
Show resolved
Hide resolved
898d5ad
to
4416991
Compare
4416991
to
292b144
Compare
tests/acceptance/features/apiSharingNg/shareInvitations.feature
Outdated
Show resolved
Hide resolved
292b144
to
52feb4e
Compare
52feb4e
to
c4b9850
Compare
tests/acceptance/features/apiSharingNg/shareInvitations.feature
Outdated
Show resolved
Hide resolved
c4b9850
to
30e226d
Compare
f600883
to
379f884
Compare
tests/acceptance/features/apiSharingNg/shareInvitations.feature
Outdated
Show resolved
Hide resolved
379f884
to
36cc281
Compare
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.
LGTM
|
Description
Added test scenario to send share invitation to unknown group.
Expected: sharing should fail with status code
400
Added Scenario:
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: