Skip to content

Commit

Permalink
Added acceptance test for single/multiple user:sync
Browse files Browse the repository at this point in the history
  • Loading branch information
kiranparajuli589 committed Feb 3, 2020
1 parent f33e203 commit 0d95c2e
Showing 1 changed file with 31 additions and 8 deletions.
39 changes: 31 additions & 8 deletions tests/acceptance/features/cliProvisioning/userSync.feature
Original file line number Diff line number Diff line change
@@ -1,16 +1,10 @@
@cli
Feature: sync a user using occ command
Feature: sync user using occ command

As an administrator
I want to be able to sync a user via the command line
So that I can easily manage users when user LDAP is enabled

Background:
Given these users have been created with default attributes and without skeleton files:
| username |
| user0 |
| user1 |

@skipOnOcV10.3
Scenario: admin deletes ldap users and syncs only one of them
When the administrator deletes user "user0" using the occ command
Expand Down Expand Up @@ -38,4 +32,33 @@ Feature: sync a user using occ command
"""
OC\User\Database
OCA\User_LDAP\User_Proxy
"""
"""

Scenario: admin deletes ldap users and performs full sync
When the administrator deletes user "user0" using the occ command
And the administrator deletes user "user1" using the occ command
Then user "user0" should not exist
And user "user1" should not exist
When the LDAP users have been resynced
Then user "user0" should exist
And user "user1" should exist

Scenario Outline: sync a ldap user that is superstring/substring of some other ldap users
Given user "user0user1" has been created with default attributes and without skeleton files
When the administrator changes the display name of user "<target_user>" to "Test User" using the occ command
And LDAP user "<target_user>" is resynced
Then user "user0" should exist
And user "user1" should exist
And user "user0user1" should exist
And the display name of user "<target_user>" should be "<display_name>"
Examples:
| target_user | display_name |
| user0 | User Zero |
| user0user1 | Regular User |

Scenario: sync a local user
Given user "local-user" has been created with default attributes in the database user backend
When the administrator changes the display name of user "local-user" to "Test User" using the occ command
And LDAP user "local-user" is resynced
Then the command should have been successful
And user "local-user" should not exist

0 comments on commit 0d95c2e

Please sign in to comment.