-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
API test to check that share can be made with file names more than 64 chars long #33009
Conversation
Backport on: #33010 |
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.
See comments. I feel like we should check that the receiver of the shared resource can really use it, because any of that might easily be broken when the names are long.
When user "user0" shares file "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" with user "user1" using the sharing API | ||
Then the OCS status code should be "<ocs_status_code>" | ||
And the HTTP status code should be "200" | ||
And the share fields of the last share should include |
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.
Also check that user1 can access the file
When user "user0" shares file "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" with group "grp1" using the sharing API | ||
Then the OCS status code should be "<ocs_status_code>" | ||
And the HTTP status code should be "200" | ||
And the share fields of the last share should include |
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.
create user1, put them in grp1, and make sure they can access the file
| 1 | 100 | | ||
| 2 | 200 | | ||
|
||
Scenario Outline: user create a public link share of a file with file name longer than 64 chars |
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.
s/create/creates
| 1 | 100 | | ||
| 2 | 200 | | ||
|
||
Scenario Outline: user create a public link share of a folder with folder name longer than 64 chars |
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.
s/create/creates
| path | /aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog | | ||
Then the OCS status code should be "<ocs_status_code>" | ||
And the HTTP status code should be "200" | ||
And the share fields of the last share should include |
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.
put a file in the folder, and check that the public can access the file
Codecov Report
@@ Coverage Diff @@
## master #33009 +/- ##
=========================================
Coverage 64.14% 64.14%
Complexity 18721 18721
=========================================
Files 1185 1185
Lines 70454 70454
Branches 1270 1270
=========================================
Hits 45195 45195
Misses 24889 24889
Partials 370 370
Continue to review full report at Codecov.
|
a76b274
to
bca48a2
Compare
bca48a2
to
6def591
Compare
6def591
to
4be3530
Compare
Description
This PR adds tests for sharing of files and folders with name longer than 64 characters
Related issue: #32763
How Has This Been Tested?
Locally
Types of changes
Checklist: