VladPolskiy/nextcloud-tables
1
0
Fork 0
mirror of https://github.com/nextcloud/tables.git synced 2025-08-16 15:17:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

test(integration): add case on create context with inaccessible view

Browse Source 
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
This commit is contained in:
Arthur Schiwon
2024-04-26 11:43:22 +02:00
parent f63f18c824
commit 6454df08c3
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
tests/integration/features/APIv2.feature
View File

@ -129,6 +129,18 @@ Feature: APIv2
And user "participant1-v2" fetches all Contexts
Then they will find Contexts "" and no other
@api2 @contexts
Scenario: Attempt to create a context containing an inaccessible view
Given table "Table 1 via api v2" with emoji "👋" exists for user "participant1-v2" as "t1" via v2
And table "Table 2 via api v2" with emoji "👋" exists for user "participant2-v2" as "t2" via v2
And user "participant2-v2" create view "v2" with emoji "⚡️" for "t2" as "v2"
When user "participant1-v2" attempts to create the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| v2 | view | read,create,update |
Then the reported status is "403"
And user "participant1-v2" fetches all Contexts
Then they will find Contexts "" and no other
@api2 @contexts
Scenario: Fetch the overview over existing Contexts as owner
Given table "Table 1 via api v2" with emoji "👋" exists for user "participant1-v2" as "t1" via v2