VladPolskiy/nextcloud-tables
1
0
Fork 0
mirror of https://github.com/nextcloud/tables.git synced 2025-08-18 08:19:08 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
9e394fb26d8436eb7431bc3b2fa9f228e69864d7
nextcloud-tables/tests/integration/features/APIv2.feature
Arthur Schiwon 9e394fb26d ci(integration): tests against context updates 
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
2024-06-04 11:41:42 +02:00

338 lines
20 KiB
Gherkin
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Feature: APIv2
Background:
Given user "participant1-v2" exists
Given user "participant2-v2" exists
Given user "participant3-v2" exists
@api2
Scenario: Test initial setup
Then user "participant1-v2" has the following tables via v2
| Tutorial |
Then user "participant1-v2" has the following resources via v2
| Tutorial |
@api2
Scenario: Basic table actions
Given table "Table 1 via api v2" with emoji "👋" exists for user "participant1-v2" as "t1" via v2
Then user "participant1-v2" has the following tables via v2
| Table 1 via api v2 |
And user "participant1-v2" sees the following table attributes on table "t1"
| archived | 0 |
Then user "participant1-v2" updates table "t1" set title "updated title" and emoji "⛵︎" via v2
Then user "participant1-v2" has the following tables via v2
| updated title |
Then user "participant1-v2" updates table "t1" set archived 1 via v2
And user "participant1-v2" sees the following table attributes on table "t1"
| archived | 1 |
Then user "participant1-v2" updates table "t1" set archived 0 via v2
And user "participant1-v2" sees the following table attributes on table "t1"
| archived | 0 |
Then user "participant1-v2" deletes table "t1" via v2
@api2
Scenario: Favorite tables
Given table "Own table" with emoji "👋" exists for user "participant1-v2" as "t1" via v2
And user "participant1-v2" shares table with user "participant2-v2"
And user "participant1-v2" adds the table "t1" to favorites
And user "participant1-v2" sees the following table attributes on table "t1"
| favorite | 1 |
And user "participant2-v2" fetches table info for table "t1"
And user "participant2-v2" sees the following table attributes on table "t1"
| favorite | 0 |
When user "participant1-v2" removes the table "t1" from favorites
And user "participant1-v2" sees the following table attributes on table "t1"
| favorite | 0 |
When user "participant3-v2" adds the table "t1" to favorites
Then the last response should have a "403" status code
@api2
Scenario: Basic column actions
Given table "Table 2" with emoji "👋" exists for user "participant1-v2" as "t2" via v2
Then column from main type "text" for node type "table" and node name "t2" exists with name "c1" and following properties via v2
| subtype | line |
| title | Beautiful text column |
| mandatory | 0 |
| description | This is a description! |
Then column from main type "text" for node type "table" and node name "t2" exists with name "c2" and following properties via v2
| subtype | rich |
| title | Rich is cool |
| mandatory | 1 |
| description | Another description |
Then column from main type "number" for node type "table" and node name "t2" exists with name "c3" and following properties via v2
| title | Counter |
| mandatory | 0 |
Then column from main type "number" for node type "table" and node name "t2" exists with name "c4" and following properties via v2
| subtype | progress |
| title | Progress |
Then column from main type "number" for node type "table" and node name "t2" exists with name "c5" and following properties via v2
| subtype | check |
| title | Checking |
Then column from main type "datetime" for node type "table" and node name "t2" exists with name "c6" and following properties via v2
| subtype | date |
| title | A single date |
| datetimeDefault | today |
Then node with node type "table" and node name "t2" has the following columns via v2
| Beautiful text column | Rich is cool | Counter | Progress | Checking | A single date |
Then print register
@api2selection
Scenario: Create selection columns
Given table "Table 3" with emoji "👋" exists for user "participant1-v2" as "t3" via v2
Then column from main type "selection" for node type "table" and node name "t3" exists with name "sel-c1" and following properties via v2
| title | sel single |
| selectionOptions | [{"id": 1, "label": "first"},{"id": 2, "label": "second"}] |
| selectionDefault | 2 |
Then column from main type "selection" for node type "table" and node name "t3" exists with name "sel-c2" and following properties via v2
| title | sel multi |
| subtype | multi |
| selectionOptions | [{"id": 1, "label": "first"},{"id": 2, "label": "second"}] |
| selectionDefault | ["1","2"] |
Then node with node type "table" and node name "t3" has the following columns via v2
| sel single | sel multi |
Then print register
@api2transfer
Scenario: Create selection columns
Given table "Table 4" with emoji "👋" exists for user "participant1-v2" as "t4" via v2
Then table "t4" is owned by "participant1-v2"
Then change owner for table "t4" from user "participant1-v2" to user "participant2-v2"
Then table "t4" is owned by "participant2-v2"
@api2 @contexts
Scenario: Create a simple context containing one table and one 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 "participant1-v2" as "t2" via v2
And user "participant1-v2" create view "v1" with emoji "⚡️" for "t1" as "v1"
When user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,create,update |
| v1 | view | read |
Then user "participant1-v2" has access to Context "c1"
And the fetched Context "c1" has following data:
| field | value |
| name | Enchanting Guitar |
| icon | tennis |
| node | table:t1:read,create,update |
| node | view:v1:read |
| page | startpage:2 |
@api2 @contexts
Scenario: Attempt to create a context containing an inaccessible table
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
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 |
| t2 | table | 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: 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
And table "Table 2 via api v2" with emoji "📸" exists for user "participant1-v2" as "t2" via v2
And table "Table X via api v2" with emoji "📋" exists for user "participant2-v2" as "t3" via v2
And user "participant1-v2" create view "v1" with emoji "⚡️" for "t1" as "v1"
And user "participant1-v2" create view "v2" with emoji "🦉" for "t2" as "v2"
And user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,created,update |
| v1 | view | read |
And user "participant1-v2" creates the Context "c2" with name "Placid Ring" with icon "headphones" and description "Lacus suspendisse faucibus etc pp" and nodes:
| alias | type | permissions |
| t2 | table | read,create,update |
| v2 | view | read |
And user "participant2-v2" creates the Context "c3" with name "Chilly Lumber" with icon "monitor" and description "Sed blandit libero etc pp" and nodes:
| alias | type | permissions |
| t3 | table | all |
When user "participant1-v2" fetches all Contexts
Then they will find Contexts "c1, c2" and no other
@api2 @contexts
Scenario: Fetch the a specific Context as owner
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 "participant1-v2" as "t2" via v2
And table "Table X via api v2" with emoji "📋" exists for user "participant2-v2" as "t3" via v2
And user "participant1-v2" create view "v1" with emoji "⚡️" for "t1" as "v1"
And user "participant1-v2" create view "v2" with emoji "🦉" for "t2" as "v2"
And user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,created,update |
| v1 | view | read |
And user "participant1-v2" creates the Context "c2" with name "Placid Ring" with icon "headphones" and description "Lacus suspendisse faucibus etc pp" and nodes:
| alias | type | permissions |
| t2 | table | read,create,update |
| v2 | view | read |
And user "participant2-v2" creates the Context "c3" with name "Chilly Lumber" with icon "monitor" and description "Sed blandit libero etc pp" and nodes:
| alias | type | permissions |
| t3 | table | all |
When user "participant1-v2" fetches Context "c2"
Then known Context "c2" has "name" set to "Placid Ring"
And known Context "c2" has "icon" set to "headphones"
And known Context "c2" has "description" set to "Lacus suspendisse faucibus etc pp"
And known Context "c2" contains "table" "t2" with permissions "read,create,update"
And known Context "c2" contains "view" "v2" with permissions "read"
@api2 @contexts
Scenario: Fetch a specific, but inaccessible Context
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 "participant1-v2" as "t2" via v2
And user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,created,update |
When user "participant2-v2" attempts to fetch Context "c1"
Then the reported status is "404"
@api2 @contexts
Scenario: Fetch a specific, but non-existing Context
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 "participant1-v2" as "t2" via v2
And user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,created,update |
When user "participant1-v2" attempts to fetch Context "NON-EXISTENT"
Then the reported status is "404"
@api2 @contexts
Scenario: Delete an owned context
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 "participant1-v2" as "t2" via v2
And user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,created,update |
When user "participant1-v2" deletes Context "c1"
Then the reported status is "200"
When user "participant1-v2" attempts to fetch Context "c1"
Then the reported status is "404"
@api2 @contexts
Scenario: Delete an inaccessible context
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 "participant1-v2" as "t2" via v2
And user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,created,update |
When user "participant2-v2" attempts to delete Context "c1"
Then the reported status is "404"
When user "participant2-v2" attempts to fetch Context "c1"
Then the reported status is "404"
When user "participant1-v2" fetches Context "c1"
Then the reported status is "200"
@api2 @contexts
Scenario: Delete an non-existing context
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 "participant1-v2" as "t2" via v2
And user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,created,update |
When user "participant1-v2" attempts to delete Context "NON-EXISTENT"
Then the reported status is "404"
When user "participant1-v2" attempts to fetch Context "NON-EXISTENT"
Then the reported status is "404"
@api2 @contexts @contexts-update
Scenario: Update an owned context
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 "participant1-v2" as "t2" via v2
And user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,created,update |
When user "participant1-v2" updates Context "c1" by setting
| property | value |
| name | Psychedelic Drawer |
| iconName | thermostat |
| description | Roll With the Punches |
Then the reported status is "200"
When user "participant1-v2" fetches Context "c1"
Then known Context "c1" has "name" set to "Psychedelic Drawer"
And known Context "c1" has "icon" set to "thermostat"
And known Context "c1" has "description" set to "Roll With the Punches"
@api2 @contexts @contexts-update
Scenario: Update an inaccessible context
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 "participant1-v2" as "t2" via v2
And user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,created,update |
When user "participant2-v2" updates Context "c1" by setting
| property | value |
| name | Psychedelic Drawer |
| iconName | thermostat |
| description | Roll With the Punches |
Then the reported status is "404"
When user "participant1-v2" fetches Context "c1"
Then known Context "c1" has "name" set to "Enchanting Guitar"
And known Context "c1" has "icon" set to "tennis"
And known Context "c1" has "description" set to "Lorem ipsum dolor etc pp"
@api2 @contexts @contexts-update
Scenario: Add a table to an owned context
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 "participant1-v2" as "t2" via v2
And user "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,create,update |
When user "participant1-v2" updates the nodes of the Context "c1" to
| alias | type | permissions |
| t1 | table | read,create,update |
| t2 | table | read |
Then the reported status is "200"
When user "participant1-v2" fetches Context "c1"
Then the fetched Context "c1" has following data:
| field | value |
| node | table:t1:read,create,update |
| node | table:t2:read |
@api2 @contexts @contexts-update
Scenario: Add a table to an inaccessible context
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 "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,create,update |
When user "participant2-v2" updates the nodes of the Context "c1" to
| alias | type | permissions |
| t1 | table | read,create |
| t2 | table | read |
Then the reported status is "404"
When user "participant1-v2" fetches Context "c1"
Then the fetched Context "c1" has following data:
| field | value |
| node | table:t1:read,create,update |
@api2 @contexts @contexts-update
Scenario: Add an inaccessible table to an owned context
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 "participant1-v2" creates the Context "c1" with name "Enchanting Guitar" with icon "tennis" and description "Lorem ipsum dolor etc pp" and nodes:
| alias | type | permissions |
| t1 | table | read,created,update |
When user "participant1-v2" updates the nodes of the Context "c1" to
| alias | type | permissions |
| t1 | table | read,create,update |
| t2 | table | read |
Then the reported status is "200"
When user "participant1-v2" fetches Context "c1"
Then the fetched Context "c1" has following data:
| field | value |
| node | table:t1:read,create,update |
And the fetched Context "c1" does not contain following data:
| field | value |
| node | table:t2:read |
Reference in New Issue View Git Blame Copy Permalink