fix tests

tests/acceptance/features/apiSpaces/changeSpaces.feature

@@ -51,7 +51,7 @@ Feature: Change data of space
 
   Scenario Outline: user other than space manager role can't change the name of a Space via the Graph API
     When user "<user>" changes the name of the "Project Jupiter" space to "Project Jupiter"
-    Then the HTTP status code should be "403"
+    Then the HTTP status code should be "404"
     Examples:
       | user  |
       | Brian |
@@ -90,7 +90,7 @@ Feature: Change data of space
 
   Scenario Outline: viewer and editor cannot change the description(subtitle) of a space via the Graph API
     When user "<user>" changes the description of the "Project Jupiter" space to "The Death Star is a fictional mobile space station"
-    Then the HTTP status code should be "403"
+    Then the HTTP status code should be "404"
     Examples:
       | user  |
       | Brian |
@@ -334,7 +334,7 @@ Feature: Change data of space
     Given user "Alice" has created a folder ".space" in space "Project Jupiter"
     And user "Alice" has uploaded a file inside space "Project Jupiter" with content "" to ".space/someImageFile.jpg"
     When user "Bob" sets the file ".space/someImageFile.jpg" as a space image in a special section of the "Project Jupiter" space
-    Then the HTTP status code should be "403"
+    Then the HTTP status code should be "404"
 
 
   Scenario Outline: user set new readme file as description of the space via the graph API

tests/acceptance/features/apiSpaces/disableAndDeleteSpaces.feature

@@ -41,7 +41,7 @@ Feature: Disabling and deleting space
   Scenario Outline: user with role user and guest cannot disable other space via the Graph API
     Given the administrator has given "Carol" the role "<role>" using the settings api
     When user "Carol" tries to disable a space "Project Moon" owned by user "Alice"
-    Then the HTTP status code should be "403"
+    Then the HTTP status code should be "404"
     And the user "Brian" should have a space called "Project Moon"
     And the user "Bob" should have a space called "Project Moon"
     Examples:
@@ -115,7 +115,7 @@ Feature: Disabling and deleting space
     Given the administrator has given "Carol" the role "<role>" using the settings api
     And user "Alice" has disabled a space "Project Moon"
     When user "Carol" tries to delete a space "Project Moon" owned by user "Alice"
-    Then the HTTP status code should be "403"
+    Then the HTTP status code should be "404"
     Examples:
       | role  |
       | User  |

tests/acceptance/features/apiSpaces/spaceManagement.feature

@@ -113,7 +113,7 @@ Feature: Space management
 
   Scenario: user without space admin permission tries to change the name of the project space
     When user "Carol" tries to change the name of the "Project" space to "New Name" owned by user "Alice"
-    Then the HTTP status code should be "403"
+    Then the HTTP status code should be "404"
     And the user "Alice" should have a space called "Project"
 
   @skipOnStable2.0
@@ -140,7 +140,7 @@ Feature: Space management
   Scenario: user without space admin permission tries to change the description of the project space
     Given user "Alice" has changed the description of the "Project" space to "old description"
     When user "Carol" tries to change the description of the "Project" space to "New description" owned by user "Alice"
-    Then the HTTP status code should be "403"
+    Then the HTTP status code should be "404"
 
   @skipOnStable2.0
   Scenario: space admin user disables the project space
@@ -151,12 +151,12 @@ Feature: Space management
 
   Scenario: user without space admin permission tries to disable the project space
     When user "Carol" tries to disable a space "Project" owned by user "Alice"
-    Then the HTTP status code should be "403"
+    Then the HTTP status code should be "404"
 
 
   Scenario Outline: space admin user tries to disable the personal space
     When user "<user>" disables a space "Alice Hansen" owned by user "Alice"
-    Then the HTTP status code should be "403"
+    Then the HTTP status code should be "404"
     Examples:
       | user  |
       | Brian |
@@ -173,7 +173,7 @@ Feature: Space management
   Scenario: user without space admin permission tries to delete the project space
     Given user "Alice" has disabled a space "Project"
     When user "Carol" tries to delete a space "Project" owned by user "Alice"
-    Then the HTTP status code should be "403"
+    Then the HTTP status code should be "404"
 
   @skipOnStable2.0
   Scenario: space admin user enables the project space