From 84c742b95e338ebd61e8c4b829cf61913ad386dc Mon Sep 17 00:00:00 2001 From: Lukas Reschke Date: Wed, 31 Aug 2016 10:40:17 +0200 Subject: [PATCH] Use "testing" instead of "user_ldap" as test app --- build/integration/features/provisioning-v1.feature | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/build/integration/features/provisioning-v1.feature b/build/integration/features/provisioning-v1.feature index 63f8bcec5c..785b795bf3 100644 --- a/build/integration/features/provisioning-v1.feature +++ b/build/integration/features/provisioning-v1.feature @@ -305,19 +305,19 @@ Feature: provisioning Scenario: enable an app Given As an "admin" - And app "user_ldap" is disabled - When sending "POST" to "/cloud/apps/user_ldap" + And app "testing" is disabled + When sending "POST" to "/cloud/apps/testing" Then the OCS status code should be "100" And the HTTP status code should be "200" - And app "user_ldap" is enabled + And app "testing" is enabled Scenario: disable an app Given As an "admin" - And app "user_ldap" is enabled - When sending "DELETE" to "/cloud/apps/user_ldap" + And app "testing" is enabled + When sending "DELETE" to "/cloud/apps/testing" Then the OCS status code should be "100" And the HTTP status code should be "200" - And app "user_ldap" is disabled + And app "testing" is disabled Scenario: disable an user Given As an "admin"