Acceptance test for creating password with emoji

owncloud · May 24, 2019 · 5607d77 · 5607d77
1 parent 30a974c
commit 5607d77
Show file tree

Hide file tree

Showing 3 changed files with 33 additions and 1 deletion.
diff --git a/tests/acceptance/features/apiProvisioning-v1/resetUserPassword.feature b/tests/acceptance/features/apiProvisioning-v1/resetUserPassword.feature
@@ -71,3 +71,19 @@ 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"
+
+  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
+    Examples:
+      | password        | comment  |
+      | 😛 😜           | smileys  |
+      | 🐶🐱 🐭           | Animals  |
+      | ⌚️ 📱 📲 💻           | objects  |
+      | 🚴🏿‍♀️ 🚴‍♂️            | cycling |
+    But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"
diff --git a/tests/acceptance/features/apiProvisioning-v2/resetUserPassword.feature b/tests/acceptance/features/apiProvisioning-v2/resetUserPassword.feature
@@ -71,3 +71,19 @@ 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"
+
+  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
+    Examples:
+      | password        | comment  |
+      | 😛 😜           | smileys  |
+      | 🐶🐱 🐭           | Animals  |
+      | ⌚️ 📱 📲 💻           | objects  |
+      | 🚴🏿‍♀️ 🚴‍♂️            | cycling |
+    But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"
diff --git a/tests/acceptance/features/webUIPersonalSettings/changePasswordFromSetting.feature b/tests/acceptance/features/webUIPersonalSettings/changePasswordFromSetting.feature
@@ -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"