github.com/DerekStrickland/consul@v1.4.5/ui-v2/tests/acceptance/deleting.feature (about) 1 @setupApplicationTest 2 Feature: deleting: Deleting items with confirmations, success and error notifications 3 In order to delete items in consul 4 As a user 5 I should be able to delete items, get confirmation or a error notification that it has or has not been deleted 6 Background: 7 Given 1 datacenter model with the value "datacenter" 8 Scenario: Deleting a [Edit] model from the [Listing] listing page 9 Given 1 [Edit] model from json 10 --- 11 [Data] 12 --- 13 When I visit the [Listing] page for yaml 14 --- 15 dc: datacenter 16 --- 17 And I click actions on the [Listing] 18 And I click delete on the [Listing] 19 And I click confirmDelete on the [Listing] 20 Then a [Method] request is made to "[URL]" 21 And "[data-notification]" has the "notification-delete" class 22 And "[data-notification]" has the "success" class 23 When I visit the [Edit] page for yaml 24 --- 25 dc: datacenter 26 [Slug] 27 --- 28 Given the url "[URL]" responds with a 500 status 29 And I click delete 30 And I click confirmDelete 31 And "[data-notification]" has the "notification-delete" class 32 And "[data-notification]" has the "error" class 33 Where: 34 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 35 | Edit | Listing | Method | URL | Data | Slug | 36 # | acl | acls | PUT | /v1/acl/destroy/something?dc=datacenter | {"Name": "something", "ID": "something"} | acl: something | 37 | kv | kvs | DELETE | /v1/kv/key-name?dc=datacenter | ["key-name"] | kv: key-name | 38 | intention | intentions | DELETE | /v1/connect/intentions/ee52203d-989f-4f7a-ab5a-2bef004164ca?dc=datacenter | {"SourceName": "name", "ID": "ee52203d-989f-4f7a-ab5a-2bef004164ca"} | intention: ee52203d-989f-4f7a-ab5a-2bef004164ca | 39 | token | tokens | DELETE | /v1/acl/token/001fda31-194e-4ff1-a5ec-589abf2cafd0?dc=datacenter | {"AccessorID": "001fda31-194e-4ff1-a5ec-589abf2cafd0"} | token: 001fda31-194e-4ff1-a5ec-589abf2cafd0 | 40 | policy | policies | DELETE | /v1/acl/policy/1981f51d-301a-497b-89a0-05112ef02b4b?dc=datacenter | {"ID": "1981f51d-301a-497b-89a0-05112ef02b4b"} | policy: 1981f51d-301a-497b-89a0-05112ef02b4b | 41 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 42 Scenario: Deleting a [Model] from the [Model] detail page 43 When I visit the [Model] page for yaml 44 --- 45 dc: datacenter 46 [Slug] 47 --- 48 And I click delete 49 And I click confirmDelete 50 Then a [Method] request is made to "[URL]" 51 And "[data-notification]" has the "notification-delete" class 52 And "[data-notification]" has the "success" class 53 When I visit the [Model] page for yaml 54 --- 55 dc: datacenter 56 [Slug] 57 --- 58 Given the url "[URL]" responds with a 500 status 59 And I click delete 60 And I click confirmDelete 61 And "[data-notification]" has the "notification-delete" class 62 And "[data-notification]" has the "error" class 63 Where: 64 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 65 | Model | Method | URL | Data | Slug | 66 # | acl | PUT | /v1/acl/destroy/something?dc=datacenter | {"Name": "something", "ID": "something"} | acl: something | 67 | kv | DELETE | /v1/kv/key-name?dc=datacenter | ["key-name"] | kv: key-name | 68 | intention | DELETE | /v1/connect/intentions/ee52203d-989f-4f7a-ab5a-2bef004164ca?dc=datacenter | {"SourceName": "name", "ID": "ee52203d-989f-4f7a-ab5a-2bef004164ca"} | intention: ee52203d-989f-4f7a-ab5a-2bef004164ca | 69 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 70 @ignore 71 Scenario: Sort out the wide tables ^ 72 Then ok