Scenario Outline: the administrator can edit a user display (the API allows editing the "display name" by using the key word "display") # /var/www/owncloud/testrunner/apps/user_ldap/tests/acceptance/features/apiProvisioningLDAP/users.feature:47
    Given using OCS API version "<ocs-api-version>"                                                                                       # FeatureContext::usingOcsApiVersion()
    And user "Alice" has been created with default attributes in the database user backend                                                # FeatureContext::userHasBeenCreatedOnDatabaseBackend()
    When the administrator changes the display of user "Alice" to "A New User" using the provisioning API                                 # FeatureContext::adminChangesTheDisplayOfUserUsingTheProvisioningApi()
    Then the OCS status code should be "<ocs-status-code>"                                                                                # OCSContext::theOCSStatusCodeShouldBe()
    And the HTTP status code should be "<http-status-code>"                                                                               # FeatureContext::thenTheHTTPStatusCodeShouldBe()
    And the display name of user "Alice" should be "A New User"                                                                           # FeatureContext::theDisplayNameOfUserShouldBe()

    Examples:
      | ocs-api-version | ocs-status-code | http-status-code |
      | 1               | 100             | 200              |
        Failed asserting that two strings are equal.
        --- Expected
        +++ Actual
        @@ @@
        -'A New User'
        +'Alice Hansen'
      | 2               | 200             | 200              |
        Failed asserting that two strings are equal.
        --- Expected
        +++ Actual
        @@ @@
        -'A New User'
        +'Alice Hansen'

   And user "Alice" has been created with default attributes in the database user backend