2017-01-18 23:13:23 +03:00
|
|
|
Feature: LDAP
|
|
|
|
|
|
|
|
|
|
Scenario: Creating an new, empty configuration
|
|
|
|
|
Given As an "admin"
|
|
|
|
|
When sending "POST" to "/apps/user_ldap/api/v1/config"
|
|
|
|
|
Then the OCS status code should be "100"
|
|
|
|
|
And the HTTP status code should be "200"
|
2017-01-19 12:04:15 +03:00
|
|
|
And the response should contain a tag "configID"
|
2017-01-19 01:17:58 +03:00
|
|
|
|
|
|
|
|
Scenario: Delete a non-existing configuration
|
|
|
|
|
Given As an "admin"
|
|
|
|
|
When sending "DELETE" to "/apps/user_ldap/api/v1/config/s666"
|
|
|
|
|
Then the OCS status code should be "404"
|
|
|
|
|
And the HTTP status code should be "200"
|
|
|
|
|
|
|
|
|
|
Scenario: Delete an invalid configuration
|
|
|
|
|
Given As an "admin"
|
|
|
|
|
When sending "DELETE" to "/apps/user_ldap/api/v1/config/hack0r"
|
|
|
|
|
Then the OCS status code should be "400"
|
|
|
|
|
And the HTTP status code should be "200"
|
|
|
|
|
|
2017-01-19 12:04:15 +03:00
|
|
|
Scenario: Create and delete a configuration
|
|
|
|
|
Given As an "admin"
|
|
|
|
|
And creating a configuration at "/apps/user_ldap/api/v1/config"
|
|
|
|
|
When deleting the configuration
|
|
|
|
|
Then the OCS status code should be "100"
|
|
|
|
|
And the HTTP status code should be "200"
|
