-
Notifications
You must be signed in to change notification settings - Fork 21
/
APIv1.feature
260 lines (247 loc) · 12.1 KB
/
APIv1.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
Feature: APIv1
Background:
Given user "participant1" exists
Given user "participant2" exists
And group "phoenix" exists
And user "participant1" is member of group "phoenix"
And user "participant2" is member of group "phoenix"
@api1
Scenario: User has initial table
Then user "participant1" has the following tables
| Tutorial |
@api1
Scenario: User creates, rename and delete a table
Given table "my new awesome table" with emoji "🤓" exists for user "participant1" as "base1"
Then user "participant1" has the following tables
| my new awesome table |
Then user "participant1" updates table with keyword "awesome" set title "renamed table" and optional emoji "🍓"
Then user "participant1" updates table with keyword "renamed table" set title "renamed table without emoji" and optional emoji ""
Then user "participant1" deletes table with keyword "without emoji"
Then user "participant1" has the following tables
| Tutorial |
@api1
Scenario: Table sharing with a user
Given table "Ready to share" with emoji "🥪" exists for user "participant1" as "base1"
Then user "participant1" shares table with user "participant2"
Then user "participant2" has the following permissions
| read | 1 |
| create | 1 |
| update | 1 |
| delete | 0 |
| manage | 0 |
Then user "participant2" has the following tables
| Tutorial | Ready to share |
Then user "participant1" sets permission "read" to 0
Then user "participant1" sets permission "update" to 0
Then user "participant2" has the following permissions
| read | 0 |
| create | 1 |
| update | 0 |
| delete | 0 |
| manage | 0 |
Then user "participant1" deletes table with keyword "Ready to share"
Then user "participant1" has the following tables
| Tutorial |
Then user "participant2" has the following tables
| Tutorial |
@api1 @table-sharing
Scenario: Inaccessible table sharing with a user
Given table "Ready to share" with emoji "🥪" exists for user "participant1" as "base1"
And user "participant3" exists
When user "participant2" attempts to share the table with user "participant3"
Then the reported status is "404"
And user "participant3" has the following tables
| Tutorial |
@api1
Scenario: Table sharing with a group
Given table "Ready to share" with emoji "🥪" exists for user "participant1" as "base1"
Then user "participant1" shares table with group "phoenix"
Then user "participant2" has the following tables
| Tutorial | Ready to share |
Then user "participant1" deletes table with keyword "Ready to share"
Then user "participant1" has the following tables
| Tutorial |
Then user "participant2" has the following tables
| Tutorial |
@api1
Scenario: Create and check columns
Given table "Column test" with emoji "🥶" exists for user "participant1" as "base1"
Then table has at least following columns
Then column "First column" exists with following properties
| type | text |
| subtype | line |
| mandatory | 0 |
| description | This is a description! |
Then column "Resources" exists with following properties
| type | text |
| subtype | link |
| mandatory | 0 |
| textAllowedPattern | files,tables,url |
Then column "Second column" exists with following properties
| type | number |
| mandatory | 1 |
| description | Scala from 0 to 15 |
| numberMin | 0 |
| numberMax | 15 |
| numberDefault | 8 |
Then column "Third column" exists with following properties
| type | number |
| subtype | progress |
| mandatory | 0 |
| description | Progress test |
| numberDefault | 20 |
Then table has at least following columns
| First column |
| Second column |
| Third column |
| Resources |
Then set following properties for last created column
| title | Second column renamed |
| mandatory | 0 |
| description | Scala from 5 to 10 |
| numberMin | 5 |
| numberMax | 10 |
| numberDefault | 5 |
Then user deletes last created column
Then table has at least following columns
| First column |
Then user "participant1" deletes table with keyword "Column test"
@api1 @rows
Scenario: Create, modify and delete rows
Given table "Rows check" with emoji "👨🏻💻" exists for user "participant1" as "base1"
Then column "one" exists with following properties
| type | text |
| subtype | line |
| mandatory | 0 |
| description | This is a description! |
Then column "two" exists with following properties
| type | number |
| mandatory | 1 |
| numberDefault | 10 |
| description | This is a description! |
Then column "three" exists with following properties
| type | selection |
| subtype | check |
| mandatory | 1 |
| description | This is a description! |
Then column "four" exists with following properties
| type | datetime |
| subtype | date |
| mandatory | 0 |
| description | This is a description! |
Then row exists with following values
| one | AHA |
| two | 88 |
| three | true |
| four | 2023-12-24 |
Then set following values for last created row
| one | AHA! |
| two | 99 |
| three | false |
| four | 2020-02-04 |
Then user deletes last created row
Then user "participant1" deletes table with keyword "Rows check"
@api1 @rows
Scenario: Create, modify and delete rows (legacy interface)
Given table "Rows check legacy" with emoji "👨🏻💻" exists for user "participant1" as "base1"
Then column "one" exists with following properties
| type | text |
| subtype | line |
| mandatory | 0 |
| description | This is a description! |
Then column "two" exists with following properties
| type | number |
| mandatory | 1 |
| numberDefault | 10 |
| description | This is a description! |
Then column "three" exists with following properties
| type | selection |
| subtype | check |
| mandatory | 1 |
| description | This is a description! |
Then column "four" exists with following properties
| type | datetime |
| subtype | date |
| mandatory | 0 |
| description | This is a description! |
Then row exists with following values via legacy interface
| one | AHA |
| two | 88 |
| three | true |
| four | 2023-12-24 |
Then set following values for last created row via legacy interface
| one | AHA! |
| two | 99 |
| three | true |
| four | 2020-02-04 |
Then user deletes last created row
Then user "participant1" deletes table with keyword "Rows check"
@api1
Scenario: Import csv table
Given file "/import.csv" exists for user "participant1" with following data
| Col1 | Col2 | Col3 | num | emoji | special |
| Val1 | Val2 | Val3 | 1 | 💙 | Ä |
| great | news | here | 99 | ⚠️ | Ö |
Given table "Import test" with emoji "👨🏻💻" exists for user "participant1" as "base1"
When user imports file "/import.csv" into last created table
Then import results have the following data
| found_columns_count | 6 |
| created_columns_count | 6 |
| inserted_rows_count | 2 |
| errors_count | 0 |
Then table has at least following columns
| Col1 |
| Col2 |
| Col3 |
| num |
| emoji |
| special |
Then table contains at least following rows
| Col1 | Col2 | Col3 | num | emoji | special |
| Val1 | Val2 | Val3 | 1 | 💙 | Ä |
| great | news | here | 99 | ⚠️ | Ö |
@api1
Scenario: Create, edit and delete views
Given table "View test" with emoji "👨🏻💻" exists for user "participant1" as "view-test"
# Then print register
Then table "view-test" has the following views for user "participant1"
# Then print register
When user "participant1" create view "first view" with emoji "⚡️" for "view-test" as "first-view"
Then table "view-test" has the following views for user "participant1"
| first view |
# Then print register
When user "participant1" update view "first-view" with title "updated first view" and emoji "💾"
Then table "view-test" has the following views for user "participant1"
| updated first view |
When user "participant1" deletes view "first-view"
Then table "view-test" has the following views for user "participant1"
@api1 @contexts @contexts-sharing
Scenario: Share an owned context
Given table "Table 1 via api v2" with emoji "👋" exists for user "participant1" as "t1" via v2
And table "Table 2 via api v2" with emoji "📸" exists for user "participant1" as "t2" via v2
And user "participant1" 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 |
| t2 | table | read |
When user "participant2" attempts to fetch Context "c1"
Then the reported status is "404"
When user "participant1" shares the Context "c1" to "user" "participant2"
Then the reported status is "200"
When user "participant2" fetches Context "c1"
Then the fetched Context "c1" has following data:
| field | value |
| node | table:t1:read,create,update |
| node | table:t2:read |
@api1 @contexts @contexts-sharing
Scenario: Share an inaccessible context
Given table "Table 1 via api v2" with emoji "👋" exists for user "participant1" as "t1" via v2
And table "Table 2 via api v2" with emoji "📸" exists for user "participant1" as "t2" via v2
And user "participant1" 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 |
| t2 | table | read |
And user "participant3" exists
When user "participant2" shares the Context "c1" to "user" "participant3"
Then the reported status is "404"
When user "participant3" attempts to fetch Context "c1"
Then the reported status is "404"