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
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
|
Feature: Perimeter
Background:
Given the system has no rules
And the system has no subject assignments
And the system has no action assignments
And the system has no object assignments
And the system has no subject data
And the system has no action data
And the system has no object data
And the system has no subject perimeter
And the system has no object perimeter
And the system has no action perimeter
And the system has no pdps
And the system has no policies
And the system has no models
And the system has no meta-rules
And the system has no subject categories
And the system has no action categories
And the system has no object categories
And the following meta data subject category exists
| subjectmetadataname | subjectmetadatadescription |
| Affiliation: | This meta data has the categorical information about a subject |
| Authorization-Level: | This meta data has the categorical information about an object |
| Degree: | This meta data has the categorical information about an object |
And the following meta data object category exists
| objectmetadataname | objectmetadatadescription |
| Clearance: | This meta data has the categorical information about an object |
| Type: | This meta data has the categorical information about an object |
| Class: | This meta data has the categorical information about an object |
And the following meta data action category exists
| actionmetadataname | actionmetadatadescription |
| Action-Class: | This meta data has the categorical information about an action |
| Action-Priority: | This meta data has the categorical information about an action |
| Recommendation: | This meta data has the categorical information about an action |
And the following meta rule exists
| metarulename | metaruledescription | subjectmetadata | actionmetadata | objectmetadata |
| metarule1 | Thisisabasicmetarule | Affiliation: | Action-Class: | Clearance: |
| metarule2 | Thisisabasicmetarule | Authorization-Level: | Action-Class: | Clearance: |
| metarule3 | Thisisabasicmetarule | Affiliation: | Action-Priority: | Clearance: |
| metarule4 | Thisisabasicmetarule | Authorization-Level: | Action-Priority: | Clearance: |
| metarule5 | Thisisabasicmetarule | Affiliation: | Action-Class: | Type: |
| metarule6 | Thisisabasicmetarule | Authorization-Level: | Action-Class: | Type: |
| metarule7 | Thisisabasicmetarule | Affiliation: | Action-Priority: | Type: |
| metarule8 | Thisisabasicmetarule | Authorization-Level: | Action-Priority: | Type: |
| metarule9 | Thisisabasicmetarule | Affiliation:,Authorization-Level: | Action-Class:,Action-Priority: | Clearance:,Type: |
And the following model exists
| modelname | modeldescription | metarule |
| universitymodel | Thisisabasicmodel | metarule1,metarule9 |
| universitymodel2 | Thisisabasicmodel | metarule3,metarule5,metarule8 |
| universitymodel3 | Thisisabasicmodel | metarule9 |
And the following policy exists
| policyname | policydescription | modelname | genre |
| Stanford Policy | This is a basic policy | universitymodel | Education |
| Cambridge Policy | This is a basic policy | universitymodel2 | Education |
Scenario: Add subject perimeter
When the user sets to add the following subject perimeter
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Cambridge Policy |
Then the following subject perimeter should be existed in the system
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Cambridge Policy,Stanford Policy |
Scenario Outline: Add subject perimeter validations
When the user sets to add the following subject perimeter
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| <subjectperimetername> | <subjectperimeterdescription> | <subjectperimeteremail> | <subjectperimeterpassword> | <policies> |
Then the system should reply the following
| flag |
| <flag> |
Examples:
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies | flag |
| | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy | False |
| _%JohnLewis%_ | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy | True |
| JohnLewis | | jlewis@orange.com | abc1234 | Stanford Policy | True |
| JohnLewis | Thisistheexpecteduser% | jlewis@orange.com | abc1234 | Stanford Policy | True |
| JohnLewis | Thisistheexpecteduser% | jlewis@orange.com | abc1234 | | True |
Scenario Outline: Add an existing subject perimeter
Given the following subject perimeter exists
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy |
When the user sets to add the following subject perimeter
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| <subjectperimetername> | <subjectperimeterdescription> | <subjectperimeteremail> | <subjectperimeterpassword> | <policies> |
Then the system should reply the following
| flag |
| <flag> |
Examples:
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies | flag |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy | False |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Cambridge Policy | True |
Scenario: Update subject perimeter
Given the following subject perimeter exists
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Cambridge Policy |
When the user sets to update the following subject perimeter
| subjectperimetername | updatedsubjectperimetername | updatedsubjectperimeterdescription | updatedsubjectperimeteremail | updatedsubjectperimeterpassword | policies |
| JohnLewis | JoesephWilliams | Thisdatahasthevalueofsubjectperimeter | jwilliams@orange.com | abc1234 | Stanford Policy |
Then the following subject perimeter should be existed in the system
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JoesephWilliams | Thisdatahasthevalueofsubjectperimeter | jwilliams@orange.com | abc1234 | Cambridge Policy,Stanford Policy |
Scenario Outline: Update subject perimeter validations
Given the following subject perimeter exists
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy |
When the user sets to update the following subject perimeter
| subjectperimetername | updatedsubjectperimetername | updatedsubjectperimeterdescription | updatedsubjectperimeteremail | updatedsubjectperimeterpassword | policies |
| <subjectperimetername> | <updatedsubjectperimetername> | <updatedsubjectperimeterdescription> | <updatedsubjectperimeteremail> | <updatedsubjectperimeterpassword> | <policies> |
Then the system should reply the following
| flag |
| <flag> |
Examples:
| subjectperimetername | updatedsubjectperimetername | updatedsubjectperimeterdescription | updatedsubjectperimeteremail | updatedsubjectperimeterpassword | policies | flag |
#| JohnLewis | | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy | False |
| JohnLewis | _%JohnLewis%_ | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy | True |
#| JohnLewis | JohnLewis | | jlewis@orange.com | abc1234 | Stanford Policy | True |
#| JohnLewis | JohnLewis | Thisistheexpecteduser% | jlewis@orange.com | abc1234 | Stanford Policy | True |
Scenario: Delete subject perimeter with a policy and no assignments
Given the following subject perimeter exists
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy |
When the user sets to delete the following subject perimeter
| subjectperimetername |
| JohnLewis |
Then the system should reply the following
| flag |
| False |
And the following subject perimeter should be existed in the system
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy |
Scenario: Check subject perimeter after removing the policy
Given the following subject perimeter exists
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy |
When the user sets to delete the following subject perimeter for a given policy
| subjectperimetername | policies |
| JohnLewis | Stanford Policy |
Then the following subject perimeter should be existed in the system
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | |
Scenario: Delete subject perimeter with no policy
Given the following subject perimeter exists
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy |
When the user sets to delete the following subject perimeter for a given policy
| subjectperimetername | policies |
| JohnLewis | Stanford Policy |
And the user sets to delete the following subject perimeter
| subjectperimetername |
| JohnLewis |
Then the following subject perimeter should be existed in the system
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| | | | | |
Scenario: Delete subject perimeter with a policy and with assignments
Given the following subject perimeter exists
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | Stanford Policy |
And the following subject data exists
| policyname | subjectcategory | subjectdataname | subjectdatadescription |
| Stanford Policy | Affiliation: | University-of-Stanford | This data has the value of subject category |
| Stanford Policy | Affiliation: | Stanford | This data has the value of subject category |
And the following subject assignment exists
| subjectperimetername | subjectcategory | subjectdata | policyname |
| JohnLewis | Affiliation: | University-of-Stanford | Stanford Policy |
| JohnLewis | Affiliation: | Stanford | Stanford Policy |
When the user sets to delete the following subject perimeter for a given policy
| subjectperimetername | policies |
| JohnLewis | Stanford Policy |
Then the system should reply the following
| flag |
| True |
And the following subject perimeter should be existed in the system
| subjectperimetername | subjectperimeterdescription | subjectperimeteremail | subjectperimeterpassword | policies |
| JohnLewis | Thisistheexpecteduser | jlewis@orange.com | abc1234 | |
And the following subject assignment should be existed in the system
| subjectperimetername | subjectcategory | subjectdata | policyname |
| | | | Stanford Policy |
Scenario: Add object perimeter
When the user sets to add the following object perimeter
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Stanford Policy |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Cambridge Policy |
Then the following object perimeter should be existed in the system
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Cambridge Policy,Stanford Policy |
Scenario Outline: Add object perimeter validations
When the user sets to add the following object perimeter
| objectperimetername | objectperimeterdescription | policies |
| <objectperimetername> | <objectperimeterdescription> | <policies> |
Then the system should reply the following
| flag |
| <flag> |
Examples:
| objectperimetername | objectperimeterdescription | policies | flag |
| | Thisistherequesttoaccessfile | Stanford Policy | False |
| _%ProfessorsPromotionDocument%_ | Thisistherequesttoaccessfile | Stanford Policy | True |
| ProfessorsPromotionDocument | | Stanford Policy | True |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile% | Stanford Policy | True |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile% | | True |
Scenario Outline: Add an existing object perimeter
Given the following object perimeter exists
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Stanford Policy |
When the user sets to add the following object perimeter
| objectperimetername | objectperimeterdescription | policies |
| <objectperimetername> | <objectperimeterdescription> | <policies> |
Then the system should reply the following
| flag |
| <flag> |
Examples:
| objectperimetername | objectperimeterdescription | policies | flag |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Stanford Policy | False |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Cambridge Policy | True |
Scenario: Update object perimeter
Given the following object perimeter exists
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Stanford Policy |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Cambridge Policy |
When the user sets to update the following object perimeter
| objectperimetername | updatedobjectperimetername | updatedobjectperimeterdescription | policies |
| ProfessorsPromotionDocument | StudentsGradsSheet | Thisistherequesttoaccessfile | Stanford Policy |
Then the following object perimeter should be existed in the system
| objectperimetername | objectperimeterdescription | policies |
| StudentsGradsSheet | Thisistherequesttoaccessfile | Cambridge Policy,Stanford Policy |
Scenario Outline: Update object perimeter validations
Given the following object perimeter exists
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Stanford Policy |
When the user sets to update the following object perimeter
| objectperimetername | updatedobjectperimetername | updatedobjectperimeterdescription | policies |
| <objectperimetername> | <updatedobjectperimetername> | <updatedobjectperimeterdescription> | <policies> |
Then the system should reply the following
| flag |
| <flag> |
Examples:
| objectperimetername | updatedobjectperimetername | updatedobjectperimeterdescription | policies | flag |
| ProfessorsPromotionDocument | | Thisistherequesttoaccessfile | Stanford Policy | False |
| ProfessorsPromotionDocument | _%ProfessorsPromotionDocument%_ | Thisistherequesttoaccessfile | Stanford Policy | True |
| ProfessorsPromotionDocument | ProfessorsPromotionDocument | | Stanford Policy | True |
| ProfessorsPromotionDocument | ProfessorsPromotionDocument | Thisistherequesttoaccessfile% | Stanford Policy | True |
Scenario: Delete object perimeter with a policy
Given the following object perimeter exists
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Stanford Policy |
When the user sets to delete the following object perimeter
| objectperimetername |
| ProfessorsPromotionDocument |
Then the system should reply the following
| flag |
| False |
And the following object perimeter should be existed in the system
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Stanford Policy |
Scenario: Check object perimeter after removing the policy
Given the following object perimeter exists
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Stanford Policy |
When the user sets to delete the following object perimeter for a given policy
| objectperimetername | policies |
| ProfessorsPromotionDocument | Stanford Policy |
Then the following object perimeter should be existed in the system
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | |
Scenario: Delete object perimeter after removing the policy
Given the following object perimeter exists
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Stanford Policy |
When the user sets to delete the following object perimeter for a given policy
| objectperimetername | policies |
| ProfessorsPromotionDocument | Stanford Policy |
And the user sets to delete the following object perimeter
| objectperimetername |
| ProfessorsPromotionDocument |
Then the following object perimeter should be existed in the system
| objectperimetername | objectperimeterdescription | policies |
| | | |
Scenario: Delete object perimeter with a policy and with assignments
Given the following object perimeter exists
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | Stanford Policy |
And the following object data exists
| policyname | objectcategory | objectdataname | objectdatadescription |
| Stanford Policy | Clearance: | Top-Secret | This data has the value of object category |
| Stanford Policy | Clearance: | Confidential | This data has the value of object category |
| Stanford Policy | Clearance: | Public | This data has the value of object category |
| Stanford Policy | Type: | Adminstrative | This data has the value of object category |
| Stanford Policy | Type: | Staff | This data has the value of object category |
And the following object assignment exists
| objectperimetername | objectcategory | objectdata | policyname |
| ProfessorsPromotionDocument | Clearance: | Public | Stanford Policy |
| ProfessorsPromotionDocument | Clearance: | Confidential | Stanford Policy |
When the user sets to delete the following object perimeter for a given policy
| objectperimetername | policies |
| ProfessorsPromotionDocument | Stanford Policy |
Then the system should reply the following
| flag |
| True |
And the following object perimeter should be existed in the system
| objectperimetername | objectperimeterdescription | policies |
| ProfessorsPromotionDocument | Thisistherequesttoaccessfile | |
And the following object assignment should be existed in the system
| objectperimetername | objectcategory | objectdata | policyname |
| | | | Stanford Policy |
Scenario: Add action perimeter
When the user sets to add the following action perimeter
| actionperimetername | actionperimeterdescription | policies |
| Read | Thisistheactionrequired | Stanford Policy |
| Read | Thisistheactionrequired | Cambridge Policy |
| Delete | Thisistheactionrequired | Stanford Policy |
| Delete | Thisistheactionrequired | Cambridge Policy |
Then the following action perimeter should be existed in the system
| actionperimetername | actionperimeterdescription | policies |
| Delete | Thisistheactionrequired | Cambridge Policy,Stanford Policy |
| Read | Thisistheactionrequired | Cambridge Policy,Stanford Policy |
Scenario Outline: Add action perimeter validations
When the user sets to add the following action perimeter
| actionperimetername | actionperimeterdescription | policies |
| <actionperimetername> | <actionperimeterdescription> | <policies> |
Then the system should reply the following
| flag |
| <flag> |
Examples:
| actionperimetername | actionperimeterdescription | policies | flag |
| | Thisistheactionrequired | Stanford Policy | False |
| _%Read%_ | Thisistheactionrequired | Stanford Policy | True |
| Read | | Stanford Policy | True |
| Read | Thisistheactionrequired% | Stanford Policy | True |
| Read | Thisistheactionrequired% | | True |
Scenario Outline: Add an existing action perimeter
Given the following action perimeter exists
| actionperimetername | actionperimeterdescription | policies |
| Read | Thisistheactionrequired | Stanford Policy |
When the user sets to add the following action perimeter
| actionperimetername | actionperimeterdescription | policies |
| <actionperimetername> | <actionperimeterdescription> | <policies> |
Then the system should reply the following
| flag |
| <flag> |
Examples:
| actionperimetername | actionperimeterdescription | policies | flag |
| Read | Thisistheactionrequired | Stanford Policy | False |
| Read | Thisistheactionrequired | Cambridge Policy | True |
Scenario: Update action perimeter
Given the following action perimeter exists
| actionperimetername | actionperimeterdescription | policies |
| Read | Thisistheactionrequired | Stanford Policy |
| Read | Thisistheactionrequired | Cambridge Policy |
When the user sets to update the following action perimeter
| actionperimetername | updatedactionperimetername | updatedactionperimeterdescription | policies |
| Read | Delete | Thisistheactionrequired | Stanford Policy |
Then the following action perimeter should be existed in the system
| actionperimetername | actionperimeterdescription | policies |
| Delete | Thisistheactionrequired | Cambridge Policy,Stanford Policy |
Scenario Outline: Update action perimeter validations
Given the following action perimeter exists
| actionperimetername | actionperimeterdescription | policies |
| Read | Thisistheactionrequired | Stanford Policy |
When the user sets to update the following action perimeter
| actionperimetername | updatedactionperimetername | updatedactionperimeterdescription | policies |
| <actionperimetername> | <updatedactionperimetername> | <updatedactionperimeterdescription> | <policies> |
Then the system should reply the following
| flag |
| <flag> |
Examples:
| actionperimetername | updatedactionperimetername | updatedactionperimeterdescription | policies | flag |
| Read | | Thisistheactionrequired | Stanford Policy | False |
| Read | _%Read%_ | Thisistheactionrequired | Stanford Policy | True |
| Read | Read | | Stanford Policy | True |
| Read | Read | Thisistheactionrequired% | Stanford Policy | True |
Scenario: Delete action perimeter with a policy
Given the following action perimeter exists
| actionperimetername | actionperimeterdescription | policies |
| Read | This is the action required | Stanford Policy |
When the user sets to delete the following action perimeter
| actionperimetername |
| Read |
Then the system should reply the following
| flag |
| False |
And the following action perimeter should be existed in the system
| actionperimetername | actionperimeterdescription | policies |
| Read | This is the action required | Stanford Policy |
Scenario: Check action perimeter after removing the policy
Given the following action perimeter exists
| actionperimetername | actionperimeterdescription | policies |
| Read | Thisistheactionrequired | Stanford Policy |
When the user sets to delete the following action perimeter for a given policy
| actionperimetername | policies |
| Read | Stanford Policy |
Then the following action perimeter should be existed in the system
| actionperimetername | actionperimeterdescription | policies |
| Read | Thisistheactionrequired | |
Scenario: Delete action perimeter after removing the policy
Given the following action perimeter exists
| actionperimetername | actionperimeterdescription | policies |
| Read | Thisistheactionrequired | Stanford Policy |
When the user sets to delete the following action perimeter for a given policy
| actionperimetername | policies |
| Read | Stanford Policy |
And the user sets to delete the following action perimeter
| actionperimetername |
| Read |
Then the following action perimeter should be existed in the system
| actionperimetername | actionperimeterdescription | policies |
| | | |
Scenario: Delete action perimeter with a policy and with assignments
Given the following action perimeter exists
| actionperimetername | actionperimeterdescription | policies |
| Read | Thisistheactionrequired | Stanford Policy |
And the following action data exists
| policyname | actioncategory | actiondataname | actiondatadescription |
| Stanford Policy | Action-Class: | Severe | This data has the value of action category |
| Stanford Policy | Action-Class: | Low | This data has the value of action category |
| Stanford Policy | Action-Priority: | Low | This data has the value of action category |
And the following action assignment exists
| actionperimetername | actioncategory | actiondata | policyname |
| Read | Action-Class: | Severe | Stanford Policy |
| Read | Action-Class: | Low | Stanford Policy |
When the user sets to delete the following action perimeter for a given policy
| actionperimetername | policies |
| Read | Stanford Policy |
Then the system should reply the following
| flag |
| True |
And the following action perimeter should be existed in the system
| actionperimetername | actionperimeterdescription | policies |
| Read | Thisistheactionrequired | |
And the following action assignment should be existed in the system
| actionperimetername | actioncategory | actiondata | policyname |
| | | | Stanford Policy |
|
