From a8649df2fa5387c76666b94729dc3311fa9677ce Mon Sep 17 00:00:00 2001 From: Kiran Parajuli Date: Thu, 6 Feb 2020 12:00:18 +0545 Subject: [PATCH] added acceptance tests for user:sync command including super/sub-stringed users --- .../features/cliProvisioning/userSync.feature | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/tests/acceptance/features/cliProvisioning/userSync.feature b/tests/acceptance/features/cliProvisioning/userSync.feature index 2378ba173..84784659a 100644 --- a/tests/acceptance/features/cliProvisioning/userSync.feature +++ b/tests/acceptance/features/cliProvisioning/userSync.feature @@ -55,3 +55,29 @@ Feature: sync user using occ command And LDAP user "local-user" is resynced Then the command should have been successful And user "local-user" should not exist + + @skipOnOcV10.3 + Scenario: sync a ldap user that is substring of some other ldap users + Given these users have been created with default attributes and without skeleton files: + | username | + | regularuser | + | regular | + When the administrator sets the ldap attribute "displayname" of the entry "uid=regular,ou=TestUsers" to "Test User" + And LDAP user "regular" is resynced + Then user "regular" should exist + And user "regularuser" should exist + And the display name of user "regular" should be "Test User" + And the display name of user "regularuser" should be "Regular User" + + @skipOnOcV10.3 + Scenario: sync a ldap user that is superstring of some other ldap users + Given these users have been created with default attributes and without skeleton files: + | username | + | regularuser | + | regular | + When the administrator sets the ldap attribute "displayname" of the entry "uid=regularuser,ou=TestUsers" to "Test User" + And LDAP user "regularuser" is resynced + Then user "regular" should exist + And user "regularuser" should exist + And the display name of user "regularuser" should be "Test User" + And the display name of user "regular" should be "Regular User"