sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial QSfera import

Browse Source
This commit is contained in:
Курнат Андрей
2026-06-07 10:20:04 +03:00
commit 2315f25754
16485 changed files with 4826827 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Server/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareResourceCaseSensitiveName.feature
+300
View File
@@ -0,0 +1,300 @@
@skipOnReva
Feature: Sharing resources with different case names with the sharee and checking the coexistence of resources on sharee/receivers side
As a user
I want to share resources with case sensitive names
So that I can make sure that the shares aren't case sensitive
Background:
Given these users have been created with default attributes:
| username |
| Alice |
| Brian |
And user "Brian" has disabled auto-accepting
Scenario: sharing files with different case names with an internal user
Given user "Alice" has uploaded the following files with content "some data"
| path |
| textfile.txt |
| text_file.txt |
| 123textfile.txt |
| textfile.XYZ.txt |
| TEXTFILE.txt |
| TEXT_FILE.txt |
| 123TEXTFILE.txt |
| TEXTFILE.xyz.txt |
When user "Alice" shares the following files with user "Brian" using the sharing API
| path |
| textfile.txt |
| text_file.txt |
| 123textfile.txt |
| textfile.XYZ.txt |
| TEXTFILE.txt |
| TEXT_FILE.txt |
| 123TEXTFILE.txt |
| TEXTFILE.xyz.txt |
And user "Brian" accepts the following shares offered by user "Alice" using the sharing API
| path |
| /textfile.txt |
| /text_file.txt |
| /123textfile.txt |
| /textfile.XYZ.txt |
| /TEXTFILE.txt |
| /TEXT_FILE.txt |
| /123TEXTFILE.txt |
| /TEXTFILE.xyz.txt |
Then the OCS status code of responses on all endpoints should be "100"
And the HTTP status code of responses on all endpoints should be "200"
And as "Brian" the following files should exist
| path |
| /Shares/textfile.txt |
| /Shares/text_file.txt |
| /Shares/123textfile.txt |
| /Shares/textfile.XYZ.txt |
| /Shares/TEXTFILE.txt |
| /Shares/TEXT_FILE.txt |
| /Shares/123TEXTFILE.txt |
| /Shares/TEXTFILE.xyz.txt |
Scenario: sharing folders with different case names with an internal user
Given user "Alice" has created the following folders
| path |
| /FO |
| /F_O |
| /123FO |
| /FO.XYZ |
| /fo |
| /f_o |
| /123fo |
| /fo.xyz |
When user "Alice" shares the following folders with user "Brian" using the sharing API
| path |
| /FO |
| /F_O |
| /123FO |
| /FO.XYZ |
| /fo |
| /f_o |
| /123fo |
| /fo.xyz |
And user "Brian" accepts the following shares offered by user "Alice" using the sharing API
| path |
| /FO |
| /F_O |
| /123FO |
| /FO.XYZ |
| /fo |
| /f_o |
| /123fo |
| /fo.xyz |
Then the OCS status code of responses on all endpoints should be "100"
And the HTTP status code of responses on all endpoints should be "200"
And as "Brian" the following folders should exist
| path |
| /Shares/FO |
| /Shares/F_O |
| /Shares/123FO |
| /Shares/FO.XYZ |
| /Shares/fo |
| /Shares/f_o |
| /Shares/123fo |
| /Shares/fo.xyz |
Scenario: sharing files and folders with different case names with an internal user
Given user "Alice" has uploaded the following files with content "some data"
| path |
| casesensitive.txt |
| case_sensitive.txt |
| 123CASE_SENSITIVE.txt |
| casesensitive.xyz.txt |
And user "Alice" has created the following folders
| path |
| /CASESENSITIVE |
| /CASE_SENSITIVE |
| /123case_sensitive |
| /CASESENSITIVE.xyz |
When user "Alice" shares the following files with user "Brian" using the sharing API
| path |
| casesensitive.txt |
| case_sensitive.txt |
| 123CASE_SENSITIVE.txt |
| casesensitive.xyz.txt |
And user "Alice" shares the following folders with user "Brian" using the sharing API
| path |
| /CASESENSITIVE |
| /CASE_SENSITIVE |
| /123case_sensitive |
| /CASESENSITIVE.xyz |
And user "Brian" accepts the following shares offered by user "Alice" using the sharing API
| path |
| /casesensitive.txt |
| /case_sensitive.txt |
| /123CASE_SENSITIVE.txt |
| /casesensitive.xyz.txt |
| /CASESENSITIVE |
| /CASE_SENSITIVE |
| /123case_sensitive |
| /CASESENSITIVE.xyz |
Then the OCS status code of responses on all endpoints should be "100"
And the HTTP status code of responses on all endpoints should be "200"
And as "Brian" the following files should exist
| path |
| /Shares/casesensitive.txt |
| /Shares/case_sensitive.txt |
| /Shares/123CASE_SENSITIVE.txt |
| /Shares/casesensitive.xyz.txt |
And as "Brian" the following folders should exist
| path |
| /Shares/CASESENSITIVE |
| /Shares/CASE_SENSITIVE |
| /Shares/123case_sensitive |
| /Shares/CASESENSITIVE.xyz |
Scenario: sharing files with different case names with group members
Given group "grp1" has been created
And user "Brian" has been added to group "grp1"
And user "Alice" has uploaded the following files with content "some data"
| path |
| textfile.txt |
| text_file.txt |
| 123textfile.txt |
| textfile.XYZ.txt |
| TEXTFILE.txt |
| TEXT_FILE.txt |
| 123TEXTFILE.txt |
| TEXTFILE.xyz.txt |
When user "Alice" shares the following files with group "grp1" using the sharing API
| path |
| textfile.txt |
| text_file.txt |
| 123textfile.txt |
| textfile.XYZ.txt |
| TEXTFILE.txt |
| TEXT_FILE.txt |
| 123TEXTFILE.txt |
| TEXTFILE.xyz.txt |
And user "Brian" accepts the following shares offered by user "Alice" using the sharing API
| path |
| /textfile.txt |
| /text_file.txt |
| /123textfile.txt |
| /textfile.XYZ.txt |
| /TEXTFILE.txt |
| /TEXT_FILE.txt |
| /123TEXTFILE.txt |
| /TEXTFILE.xyz.txt |
Then the OCS status code of responses on all endpoints should be "100"
And the HTTP status code of responses on all endpoints should be "200"
And as "Brian" the following files should exist
| path |
| /Shares/textfile.txt |
| /Shares/text_file.txt |
| /Shares/123textfile.txt |
| /Shares/textfile.XYZ.txt |
| /Shares/TEXTFILE.txt |
| /Shares/TEXT_FILE.txt |
| /Shares/123TEXTFILE.txt |
| /Shares/TEXTFILE.xyz.txt |
Scenario: sharing folders with different case names with group members
Given group "grp1" has been created
And user "Brian" has been added to group "grp1"
And user "Alice" has created the following folders
| path |
| /FO |
| /F_O |
| /123FO |
| /FO.XYZ |
| /fo |
| /f_o |
| /123fo |
| /fo.xyz |
When user "Alice" shares the following folders with group "grp1" using the sharing API
| path |
| /FO |
| /F_O |
| /123FO |
| /FO.XYZ |
| /fo |
| /f_o |
| /123fo |
| /fo.xyz |
And user "Brian" accepts the following shares offered by user "Alice" using the sharing API
| path |
| /FO |
| /F_O |
| /123FO |
| /FO.XYZ |
| /fo |
| /f_o |
| /123fo |
| /fo.xyz |
Then the OCS status code of responses on all endpoints should be "100"
And the HTTP status code of responses on all endpoints should be "200"
And as "Brian" the following folders should exist
| path |
| /Shares/FO |
| /Shares/F_O |
| /Shares/123FO |
| /Shares/FO.XYZ |
| /Shares/fo |
| /Shares/f_o |
| /Shares/123fo |
| /Shares/fo.xyz |
Scenario: sharing files and folders with different case names with group members
Given group "grp1" has been created
And user "Brian" has been added to group "grp1"
And user "Alice" has uploaded the following files with content "some data"
| path |
| casesensitive.txt |
| case_sensitive.txt |
| 123CASE_SENSITIVE.txt |
| casesensitive.xyz.txt |
And user "Alice" has created the following folders
| path |
| /CASESENSITIVE |
| /CASE_SENSITIVE |
| /123case_sensitive |
| /CASESENSITIVE.xyz |
When user "Alice" shares the following files with group "grp1" using the sharing API
| path |
| casesensitive.txt |
| case_sensitive.txt |
| 123CASE_SENSITIVE.txt |
| casesensitive.xyz.txt |
And user "Alice" shares the following folders with group "grp1" using the sharing API
| path |
| /CASESENSITIVE |
| /CASE_SENSITIVE |
| /123case_sensitive |
| /CASESENSITIVE.xyz |
And user "Brian" accepts the following shares offered by user "Alice" using the sharing API
| path |
| /casesensitive.txt |
| /case_sensitive.txt |
| /123CASE_SENSITIVE.txt |
| /casesensitive.xyz.txt |
| /CASESENSITIVE |
| /CASE_SENSITIVE |
| /123case_sensitive |
| /CASESENSITIVE.xyz |
Then the OCS status code of responses on all endpoints should be "100"
And the HTTP status code of responses on all endpoints should be "200"
And as "Brian" the following files should exist
| path |
| /Shares/casesensitive.txt |
| /Shares/case_sensitive.txt |
| /Shares/123CASE_SENSITIVE.txt |
| /Shares/casesensitive.xyz.txt |
And as "Brian" the following folders should exist
| path |
| /Shares/CASESENSITIVE |
| /Shares/CASE_SENSITIVE |
| /Shares/123case_sensitive |
| /Shares/CASESENSITIVE.xyz |
Server/tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature
+38
View File
@@ -0,0 +1,38 @@
@skipOnReva
Feature: resources shared with the same name are received with unique names
As a user
I want to share resources with same name
So that I can make sure the naming is handled properly by the server
Background:
Given using OCS API version "1"
And these users have been created with default attributes:
| username |
| Alice |
| Brian |
| Carol |
@smokeTest @issue-2131
Scenario: unique target names for incoming shares
Given user "Alice" has created folder "/foo"
And user "Brian" has created folder "/foo"
When user "Alice" shares folder "/foo" with user "Carol" using the sharing API
And user "Brian" shares folder "/foo" with user "Carol" using the sharing API
Then the OCS status code of responses on all endpoints should be "100"
And the HTTP status code of responses on all endpoints should be "200"
And user "Carol" should see the following elements
| Shares/foo |
| /Shares/foo (1) |
@smokeTest @issue-2131
Scenario: unique target names for incoming shares when auto-accepting is disabled
Given user "Brian" has disabled auto-accepting
And user "Alice" has created folder "/foo"
And user "Brian" has created folder "/foo"
When user "Alice" shares folder "/foo" with user "Carol" using the sharing API
And user "Brian" shares folder "/foo" with user "Carol" using the sharing API
Then the OCS status code of responses on all endpoints should be "100"
And the HTTP status code of responses on all endpoints should be "200"
And user "Carol" should see the following elements
| Shares/foo |
| /Shares/foo (1) |