Skip to content
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.

Sign up for GitHub

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] Fix replacement usernames #37706

Merged
merged 2 commits into from
Jul 20, 2020
+201 −158
Merged

[Tests-Only] Fix replacement usernames #37706

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a09920
Log username replacements in tests
phil-davis Jul 18, 2020
02f27b1
Make acceptance tests pass with replaced usernames
phil-davis Jul 19, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 21 additions & 21 deletions tests/acceptance/features/apiFederation1/federated.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,14 +65,14 @@ Feature: federated
When user "Brian" gets the list of pending federated cloud shares using the sharing API
Then the OCS status code should be "<ocs-status>"
And the HTTP status code should be "200"
And the fields of the last response to user "Brian" should include
And the fields of the last response about user "Alice" sharing with user "Brian" should include
| id | A_STRING |
| remote | REMOTE |
| remote_id | A_STRING |
| share_token | A_TOKEN |
| name | /textfile0.txt |
| owner | Alice |
| user | Brian |
| owner | %username% |
| user | %username% |
| mountpoint | {{TemporaryMountPointName#/textfile0.txt}} |
| accepted | 0 |
Examples:
Expand All @@ -87,14 +87,14 @@ Feature: federated
When user "Brian" retrieves the information of the last federated cloud share using the sharing API
Then the OCS status code should be "<ocs-status>"
And the HTTP status code should be "200"
And the fields of the last response to user "Brian" should include
And the fields of the last response about user "Alice" sharing with user "Brian" should include
| id | A_STRING |
| remote | REMOTE |
| remote_id | A_STRING |
| share_token | A_TOKEN |
| name | /textfile0.txt |
| owner | Alice |
| user | Brian |
| owner | %username% |
| user | %username% |
| mountpoint | /textfile0 (2).txt |
| accepted | 1 |
| type | file |
Expand All @@ -111,14 +111,14 @@ Feature: federated
When user "Brian" retrieves the information of the last pending federated cloud share using the sharing API
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs-status>"
And the fields of the last response to user "Brian" should include
And the fields of the last response about user "Alice" sharing with user "Brian" should include
| id | A_STRING |
| remote | REMOTE |
| remote_id | A_STRING |
| share_token | A_TOKEN |
| name | /textfile0.txt |
| owner | Alice |
| user | Brian |
| owner | %username% |
| user | %username% |
| mountpoint | {{TemporaryMountPointName#/textfile0.txt}} |
| accepted | 0 |
Examples:
Expand Down Expand Up @@ -303,14 +303,14 @@ Feature: federated
And user "Brian" should see the following elements
| /textfile0%20(2).txt |
When user "Brian" gets the list of federated cloud shares using the sharing API
Then the fields of the last response to user "Brian" should include
Then the fields of the last response about user "Alice" sharing with user "Brian" should include
| id | A_STRING |
| remote | REMOTE |
| remote_id | A_STRING |
| share_token | A_TOKEN |
| name | /textfile0.txt |
| owner | Alice |
| user | Brian |
| owner | %username% |
| user | %username% |
| mountpoint | /textfile0 (2).txt |
| accepted | 1 |
| type | file |
Expand Down Expand Up @@ -349,14 +349,14 @@ Feature: federated
And user "Brian" should not see the following elements
| /textfile0%20(2).txt |
When user "Brian" gets the list of pending federated cloud shares using the sharing API
Then the fields of the last response to user "Brian" should include
Then the fields of the last response about user "Alice" sharing with user "Brian" should include
| id | A_STRING |
| remote | REMOTE |
| remote_id | A_STRING |
| share_token | A_TOKEN |
| name | /textfile0.txt |
| owner | Alice |
| user | Brian |
| owner | %username% |
| user | %username% |
| mountpoint | {{TemporaryMountPointName#/textfile0.txt}} |
| accepted | 0 |
When user "Brian" gets the list of federated cloud shares using the sharing API
Expand Down Expand Up @@ -419,12 +419,12 @@ Feature: federated
When user "Brian" retrieves the information of the last federated cloud share using the sharing API
Then the OCS status code should be "<ocs-status>"
And the HTTP status code should be "200"
And the fields of the last response to user "Brian" should include
And the fields of the last response about user "Alice" sharing with user "Brian" should include
| id | A_STRING |
| remote | REMOTE |
| name | /zzzfolder |
| owner | Alice |
| user | Brian |
| owner | %username% |
| user | %username% |
| mountpoint | /zzzfolder (2) |
| type | dir |
| permissions | all |
Expand All @@ -446,14 +446,14 @@ Feature: federated
When user "Brian" retrieves the information of the last federated cloud share using the sharing API
Then the OCS status code should be "<ocs-status>"
And the HTTP status code should be "200"
And the fields of the last response to user "Brian" should include
And the fields of the last response about user "Alice" sharing with user "Brian" should include
| id | A_STRING |
| remote | REMOTE |
| remote_id | A_STRING |
| share_token | A_TOKEN |
| name | /randomfile.txt |
| owner | Alice |
| user | Brian |
| owner | %username% |
| user | %username% |
| mountpoint | /randomfile (2).txt |
| accepted | 1 |
| type | file |
Expand Down
116 changes: 58 additions & 58 deletions tests/acceptance/features/apiShareCreateSpecial1/createShareExpirationDate.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,12 +34,12 @@ Feature: a default expiration date can be specified for shares with users or gro
| expireDate | +15 days |
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
And the fields of the last response to user "Alice" should include
| share_type | user |
| file_target | /FOLDER |
| uid_owner | Alice |
| expiration | +15 days |
| share_with | Brian |
And the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | user |
| file_target | /FOLDER |
| uid_owner | %username% |
| expiration | +15 days |
| share_with | %username% |
And the response when user "Brian" gets the info of the last share should include
| expiration | +15 days |
Examples:
Expand All @@ -59,12 +59,12 @@ Feature: a default expiration date can be specified for shares with users or gro
| expireDate | +15 days |
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
And the fields of the last response to user "Alice" should include
| share_type | user |
| file_target | /FOLDER |
| uid_owner | Alice |
| share_with | Brian |
| expiration | +15 days |
And the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | user |
| file_target | /FOLDER |
| uid_owner | %username% |
| expiration | +15 days |
| share_with | %username% |
And the response when user "Brian" gets the info of the last share should include
| expiration | +15 days |
Examples:
Expand All @@ -85,12 +85,12 @@ Feature: a default expiration date can be specified for shares with users or gro
| expireDate | +15 days |
And the administrator sets parameter "shareapi_default_expire_date_user_share" of app "core" to "no"
And user "Alice" gets the info of the last share using the sharing API
Then the fields of the last response to user "Alice" should include
| share_type | user |
| file_target | /FOLDER |
| uid_owner | Alice |
| share_with | Brian |
| expiration | +15 days |
Then the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | user |
| file_target | /FOLDER |
| uid_owner | %username% |
| expiration | +15 days |
| share_with | %username% |
And the response when user "Brian" gets the info of the last share should include
| expiration | +15 days |
Examples:
Expand All @@ -111,12 +111,12 @@ Feature: a default expiration date can be specified for shares with users or gro
| permissions | read,share |
And the administrator sets parameter "shareapi_default_expire_date_user_share" of app "core" to "no"
And user "Alice" gets the info of the last share using the sharing API
Then the fields of the last response to user "Alice" should include
| share_type | user |
| file_target | /FOLDER |
| uid_owner | Alice |
| share_with | Brian |
| expiration | +7 days |
Then the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | user |
| file_target | /FOLDER |
| uid_owner | %username% |
| share_with | %username% |
| expiration | +7 days |
And the response when user "Brian" gets the info of the last share should include
| expiration | +7 days |
Examples:
Expand Down Expand Up @@ -158,12 +158,12 @@ Feature: a default expiration date can be specified for shares with users or gro
| expireDate | +15 days |
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
And the fields of the last response to user "Alice" should include
| share_type | group |
| file_target | /FOLDER |
| uid_owner | Alice |
| expiration | +15 days |
| share_with | grp1 |
And the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | group |
| file_target | /FOLDER |
| uid_owner | %username% |
| expiration | +15 days |
| share_with | grp1 |
And the response when user "Brian" gets the info of the last share should include
| expiration | +15 days |
Examples:
Expand All @@ -185,12 +185,12 @@ Feature: a default expiration date can be specified for shares with users or gro
| expireDate | +15 days |
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
And the fields of the last response to user "Alice" should include
| share_type | group |
| file_target | /FOLDER |
| uid_owner | Alice |
| expiration | +15 days |
| share_with | grp1 |
And the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | group |
| file_target | /FOLDER |
| uid_owner | %username% |
| expiration | +15 days |
| share_with | grp1 |
And the response when user "Brian" gets the info of the last share should include
| expiration | +15 days |
Examples:
Expand All @@ -213,12 +213,12 @@ Feature: a default expiration date can be specified for shares with users or gro
| expireDate | +15 days |
And the administrator sets parameter "shareapi_default_expire_date_group_share" of app "core" to "no"
And user "Alice" gets the info of the last share using the sharing API
Then the fields of the last response to user "Alice" should include
| share_type | group |
| file_target | /FOLDER |
| uid_owner | Alice |
| share_with | grp1 |
| expiration | +15 days |
Then the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | group |
| file_target | /FOLDER |
| uid_owner | %username% |
| share_with | grp1 |
| expiration | +15 days |
And the response when user "Brian" gets the info of the last share should include
| expiration | +15 days |
Examples:
Expand All @@ -242,12 +242,12 @@ Feature: a default expiration date can be specified for shares with users or gro
| expireDate | +3 days |
And the administrator sets parameter "shareapi_default_expire_date_group_share" of app "core" to "no"
And user "Alice" gets the info of the last share using the sharing API
Then the fields of the last response to user "Alice" should include
| share_type | group |
| file_target | /FOLDER |
| uid_owner | Alice |
| share_with | grp1 |
| expiration | +3 days |
Then the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | group |
| file_target | /FOLDER |
| uid_owner | %username% |
| share_with | grp1 |
| expiration | +3 days |
And the response when user "Brian" gets the info of the last share should include
| expiration | +3 days |
Examples:
Expand All @@ -262,11 +262,11 @@ Feature: a default expiration date can be specified for shares with users or gro
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes"
And user "Brian" has been created with default attributes and without skeleton files
When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
Then the fields of the last response to user "Alice" should include
Then the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | user |
| file_target | /textfile0.txt |
| uid_owner | Alice |
| share_with | Brian |
| uid_owner | %username% |
| share_with | %username% |
| expiration | +7 days |
And the response when user "Brian" gets the info of the last share should include
| expiration | +7 days |
Expand Down Expand Up @@ -304,11 +304,11 @@ Feature: a default expiration date can be specified for shares with users or gro
And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30"
And user "Brian" has been created with default attributes and without skeleton files
When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
Then the fields of the last response to user "Alice" should include
Then the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | user |
| file_target | /textfile0.txt |
| uid_owner | Alice |
| share_with | Brian |
| uid_owner | %username% |
| share_with | %username% |
| expiration | +30 days |
And the response when user "Brian" gets the info of the last share should include
| expiration | +30 days |
Expand Down Expand Up @@ -382,10 +382,10 @@ Feature: a default expiration date can be specified for shares with users or gro
And group "grp1" has been created
And user "Brian" has been added to group "grp1"
When user "Alice" shares file "textfile0.txt" with group "grp1" using the sharing API
Then the fields of the last response to user "Alice" should include
Then the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | group |
| file_target | /textfile0.txt |
| uid_owner | Alice |
| uid_owner | %username% |
| share_with | grp1 |
| expiration | +7 days |
And the response when user "Brian" gets the info of the last share should include
Expand Down Expand Up @@ -428,10 +428,10 @@ Feature: a default expiration date can be specified for shares with users or gro
And group "grp1" has been created
And user "Brian" has been added to group "grp1"
When user "Alice" shares file "textfile0.txt" with group "grp1" using the sharing API
Then the fields of the last response to user "Alice" should include
Then the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_type | group |
| file_target | /textfile0.txt |
| uid_owner | Alice |
| uid_owner | %username% |
| share_with | grp1 |
| expiration | +30 days |
And the response when user "Brian" gets the info of the last share should include
Expand Down
Loading