sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix libre-graph status codes (#7705)

Browse Source 
* fix libre-graph status codes

* owncloud-test-middleware bumped

---------

Co-authored-by: Roman Perekhod <rperekhod@owncloud.com>
This commit is contained in:
Roman Perekhod
2023-11-15 17:45:23 +01:00
committed by GitHub
co-authored by Roman Perekhod
parent 71b596e947
commit a6b75bc9f6
13 changed files with 55 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/apiGraph/createGroup.feature
+1 -1
View File
@@ -10,7 +10,7 @@ Feature: create group
Scenario Outline: admin user creates a group
When user "Alice" creates a group "<groupname>" using the Graph API
Then the HTTP status code should be "200"
Then the HTTP status code should be "201"
And group "<groupname>" should exist
Examples:
| groupname |
tests/acceptance/features/apiGraph/createUser.feature
+13 -13
View File
@@ -22,18 +22,18 @@ Feature: create user
And user "<userName>" <shouldOrNot> exist
Examples:
| userName | displayName | email | password | code | enable | shouldOrNot |
| SameDisplayName | Alice Hansen | new@example.org | containsCharacters(*:!;_+-&) | 200 | true | should |
| withoutPassSameEmail | without pass | alice@example.org | | 200 | true | should |
| name | pass with space | example@example.org | my pass | 200 | true | should |
| user1 | user names must not start with a number | example@example.org | my pass | 200 | true | should |
| SameDisplayName | Alice Hansen | new@example.org | containsCharacters(*:!;_+-&) | 201 | true | should |
| withoutPassSameEmail | without pass | alice@example.org | | 201 | true | should |
| name | pass with space | example@example.org | my pass | 201 | true | should |
| user1 | user names must not start with a number | example@example.org | my pass | 201 | true | should |
| nameWithCharacters(*:!;_+-&) | user | new@example.org | 123 | 400 | true | should not |
| name with space | name with space | example@example.org | 123 | 400 | true | should not |
| createDisabledUser | disabled user | example@example.org | 123 | 200 | false | should |
| nameWithNumbers0123456 | user | name0123456@example.org | 123 | 200 | true | should |
| name.with.dots | user | name.w.dots@example.org | 123 | 200 | true | should |
| createDisabledUser | disabled user | example@example.org | 123 | 201 | false | should |
| nameWithNumbers0123456 | user | name0123456@example.org | 123 | 201 | true | should |
| name.with.dots | user | name.w.dots@example.org | 123 | 201 | true | should |
| 123456789 | user | 123456789@example.org | 123 | 400 | true | should not |
| 0.0 | user | float@example.org | 123 | 400 | true | should not |
| withoutEmail | without email | | 123 | 200 | true | should |
| withoutEmail | without email | | 123 | 201 | true | should |
| Alice | same userName | new@example.org | 123 | 409 | true | should |
@@ -88,7 +88,7 @@ Feature: create user
| email | brian@example.com |
| password | 123 |
| accountEnabled | true |
Then the HTTP status code should be "200"
Then the HTTP status code should be "201"
And user "Brian" should exist
@@ -102,7 +102,7 @@ Feature: create user
| email | new@example.org |
| password | 123 |
| accountEnabled | true |
Then the HTTP status code should be "200"
Then the HTTP status code should be "201"
And user "<userName>" should exist
Examples:
| userName | description |
@@ -119,7 +119,7 @@ Feature: create user
| email | new@example.org |
| password | 123 |
| accountEnabled | true |
Then the HTTP status code should be "200"
Then the HTTP status code should be "201"
And user "sam" should exist
When the administrator retrieves the assigned role of user "sam" using the Graph API
Then the HTTP status code should be "200"
@@ -135,7 +135,7 @@ Feature: create user
| email | new@example.org |
| password | 123 |
| accountEnabled | true |
Then the HTTP status code should be "200"
Then the HTTP status code should be "201"
And user "sam" should exist
And user "sam" should have the role "User" assigned
@@ -147,6 +147,6 @@ Feature: create user
| email | new@example.org |
| password | 123 |
| accountEnabled | true |
Then the HTTP status code should be "200"
Then the HTTP status code should be "201"
And user "sam" should exist
And user "sam" should have the role "User" assigned
tests/acceptance/features/apiGraph/userGDPRExport.feature
+11 -11
View File
@@ -11,7 +11,7 @@ Feature: user GDPR (General Data Protection Regulation) report
Scenario: generate a GDPR report and check user data in the downloaded report
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain key 'user' and match
"""
{
@@ -74,7 +74,7 @@ Feature: user GDPR (General Data Protection Regulation) report
Scenario: generate a GDPR report and check events when a user is created
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain event type "events.UserCreated" in item 'events' and should match
"""
{
@@ -183,7 +183,7 @@ Feature: user GDPR (General Data Protection Regulation) report
Given user "Alice" has uploaded file with content "sample text" to "lorem.txt"
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain event type "events.BytesReceived" in item 'events' and should match
"""
{
@@ -309,7 +309,7 @@ Feature: user GDPR (General Data Protection Regulation) report
And user "Alice" has been added to group "tea-lover"
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain event type "events.GroupMemberAdded" in item 'events' and should match
"""
{
@@ -413,7 +413,7 @@ Feature: user GDPR (General Data Protection Regulation) report
Given user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "10000"
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain event type "events.SpaceUpdated" in item 'events' and should match
"""
{
@@ -523,7 +523,7 @@ Feature: user GDPR (General Data Protection Regulation) report
Given user "Alice" has created folder "/folderMain"
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain event type "events.ContainerCreated" in item 'events' and should match
"""
{
@@ -589,7 +589,7 @@ Feature: user GDPR (General Data Protection Regulation) report
And user "Alice" has shared entry "/folderMain" with user "Brian"
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain event type "events.ShareCreated" in item 'events' and should match
"""
{
@@ -718,7 +718,7 @@ Feature: user GDPR (General Data Protection Regulation) report
| password | %public% |
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain event type "events.LinkCreated" in item 'events' and should match
"""
{
@@ -815,7 +815,7 @@ Feature: user GDPR (General Data Protection Regulation) report
And user "Alice" has deleted folder "/folderMain"
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain event type "events.ItemTrashed" in item 'events' and should match
"""
{
@@ -862,7 +862,7 @@ Feature: user GDPR (General Data Protection Regulation) report
| role | viewer |
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain event type "events.SpaceShared" in item 'events' and should match
"""
{
@@ -962,7 +962,7 @@ Feature: user GDPR (General Data Protection Regulation) report
And user "Alice" has created a space "GDPR Space" with the default quota using the Graph API
When user "Alice" exports her GDPR report to "/.personal_data_export.json" using the Graph API
And user "Alice" downloads the content of GDPR report ".personal_data_export.json"
Then the HTTP status code of responses on each endpoint should be "201, 200" respectively
Then the HTTP status code of responses on each endpoint should be "202, 200" respectively
And the downloaded JSON content should contain event type "events.SpaceCreated" for "project" space and should match
"""
{