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

Jump to bottom

[stable10] Acceptance test for creating password with emoji #35431

Merged
merged 2 commits into from
Jun 5, 2019
Merged

[stable10] Acceptance test for creating password with emoji #35431

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
3df1150
Acceptance test for creating password with emoji
bhawanaprasain May 23, 2019
1f11044
skip tests on encryption that fail because of a known issue
individual-it Jun 5, 2019
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
17 changes: 17 additions & 0 deletions tests/acceptance/features/apiProvisioning-v1/resetUserPassword.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,3 +71,20 @@ Feature: reset user password
And the HTTP status code should be "200"
And the content of file "textfile0.txt" for user "brand-new-user" using password "%alt1%" should be "ownCloud test text file 0" plus end-of-line
But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"

@skipOnEncryptionType:user-keys @encryption-issue-57
Scenario Outline: reset user password including emoji
Given these users have been created:
| username | password | displayname | email |
| brand-new-user | %regular% | New user | brand.new.user@oc.com.np |
When the administrator resets the password of user "brand-new-user" to "<password>" using the provisioning API
Then the OCS status code should be "100"
And the HTTP status code should be "200"
And the content of file "textfile0.txt" for user "brand-new-user" using password "<password>" should be "ownCloud test text file 0" plus end-of-line
But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"
Examples:
| password | comment |
| 😛 😜 | smileys |
| 🐶🐱 🐭 | Animals |
| ⌚️ 📱 📲 💻 | objects |
| 🚴🏿‍♀️ 🚴‍♂️ | cycling |
17 changes: 17 additions & 0 deletions tests/acceptance/features/apiProvisioning-v2/resetUserPassword.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,3 +71,20 @@ Feature: reset user password
And the HTTP status code should be "200"
And the content of file "textfile0.txt" for user "brand-new-user" using password "%alt1%" should be "ownCloud test text file 0" plus end-of-line
But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"

@skipOnEncryptionType:user-keys @encryption-issue-57
Scenario Outline: reset user password including emoji
Given these users have been created:
| username | password | displayname | email |
| brand-new-user | %regular% | New user | brand.new.user@oc.com.np |
When the administrator resets the password of user "brand-new-user" to "<password>" using the provisioning API
Then the OCS status code should be "200"
And the HTTP status code should be "200"
And the content of file "textfile0.txt" for user "brand-new-user" using password "<password>" should be "ownCloud test text file 0" plus end-of-line
But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"
Examples:
| password | comment |
| 😛 😜 | smileys |
| 🐶🐱 🐭 | Animals |
| ⌚️ 📱 📲 💻 | objects |
| 🚴🏿‍♀️ 🚴‍♂️ | cycling |
2 changes: 1 addition & 1 deletion tests/acceptance/features/webUIPersonalSettings/changePasswordFromSetting.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,4 +21,4 @@ Feature: Change Login Password

Scenario: New password is same as current password
When the user changes the password to "%alt1%" using the webUI
Then a password error message should be displayed on the webUI with the text "The new password cannot be the same as the previous one"
Then a password error message should be displayed on the webUI with the text "The new password cannot be the same as the previous one"