eliott/ocis
1
0
Fork 0
mirror of https://github.com/owncloud/ocis synced 2026-04-25 17:25:21 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix: adjust tests

Browse Source
This commit is contained in:
Juan Pablo Villafáñez
2025-11-28 09:28:08 +01:00
parent 73ce507c87
commit 7003aa26c5
4 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
tests/acceptance/features/apiSpaces/changeSpaces.feature
View File

@@ -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 "404"
Then the HTTP status code should be "403"
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 "404"
Then the HTTP status code should be "403"
Examples:
| user |
| Brian |
@@ -335,7 +335,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 "404"
Then the HTTP status code should be "403"
Scenario Outline: user set new readme file as description of the space via the graph API

6
tests/acceptance/features/apiSpaces/disableAndDeleteSpaces.feature
View File

@@ -125,7 +125,7 @@ Feature: Disabling and deleting space
Given the administrator has assigned the role "<user-role>" to user "Carol" using the Graph 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 "404"
Then the HTTP status code should be "403"
Examples:
| user-role |
| User |
@@ -134,7 +134,7 @@ Feature: Disabling and deleting space
Scenario Outline: viewer and space editor cannot disable space
When user "<user>" tries to disable a space "Project Moon" owned by user "Alice"
Then the HTTP status code should be "404"
Then the HTTP status code should be "403"
And the user "<user>" should have a space called "Project Moon"
Examples:
| user |
@@ -145,7 +145,7 @@ Feature: Disabling and deleting space
Scenario Outline: viewer and space editor cannot delete disabled space
Given user "Alice" has disabled a space "Project Moon"
When user "<user>" tries to delete a space "Project Moon" owned by user "Alice"
Then the HTTP status code should be "404"
Then the HTTP status code should be "403"
Examples:
| user |
| Brian |

8
tests/acceptance/features/apiSpaces/spaceManagement.feature
View File

@@ -109,7 +109,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 "404"
Then the HTTP status code should be "403"
And the user "Alice" should have a space called "Project"
@@ -136,7 +136,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 "404"
Then the HTTP status code should be "403"
Scenario: space admin user disables the project space
@@ -152,7 +152,7 @@ Feature: Space management
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 "404"
Then the HTTP status code should be "403"
Examples:
| user |
| Brian |
@@ -169,7 +169,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 "404"
Then the HTTP status code should be "403"
Scenario: space admin user enables the project space