consul/ui-v2/tests/acceptance/dc/acls/update.feature
John Cowen 40e71f1b91
UI: Simplify/refactor the actions/notification layer (#4572) + (#4573)
* Move notification texts to a slightly different layer (#4572)
* Further Simplify/refactor the actions/notification layer (#4573)

1. Move the 'with-feedback' actions to a 'with-blocking-action' mixin
which better describes what it does
2. Additional set of unit tests almost over the entire layer to prove
things work/add confidence for further changes

The multiple 'with-action' mixins used for every 'index/edit' combo are
now reduced down to only contain the functionality related to their
specific routes, i.e. where to redirect.

The actual functionality to block and carry out the action and then
notify are 'almost' split out so that their respective classes/objects do
one thing and one thing 'well'.

Mixins are chosen for the moment as the decoration approach used by
mixins feels better than multiple levels of inheritence, but I would
like to take this fuether in the future to a 'compositional' based
approach.

There is still possible further work to be done here, but I'm a lot
happier now this is reduced down into separate parts.
2018-08-29 19:14:31 +01:00

50 lines
1.7 KiB
Gherkin

@setupApplicationTest
Feature: dc / acls / update: ACL Update
Background:
Given 1 datacenter model with the value "datacenter"
And 1 acl model from yaml
---
ID: key
---
When I visit the acl page for yaml
---
dc: datacenter
acl: key
---
Then the url should be /datacenter/acls/key
Scenario: Update to [Name], [Type], [Rules]
Then I fill in with yaml
---
name: [Name]
---
And I click "[value=[Type]]"
And I submit
Then a PUT request is made to "/v1/acl/update?dc=datacenter" with the body from yaml
---
Name: [Name]
Type: [Type]
---
Then the url should be /datacenter/acls
And "[data-notification]" has the "notification-update" class
And "[data-notification]" has the "success" class
Where:
----------------------------------------------------------
| Name | Type | Rules |
| key-name | client | node "0" {policy = "read"} |
| key name | management | node "0" {policy = "write"} |
| key%20name | client | node "0" {policy = "read"} |
| utf8? | management | node "0" {policy = "write"} |
----------------------------------------------------------
Scenario: There was an error saving the key
Given the url "/v1/acl/update" responds with a 500 status
And I submit
Then the url should be /datacenter/acls/key
Then "[data-notification]" has the "notification-update" class
And "[data-notification]" has the "error" class
# @ignore
# Scenario: Rules can be edited/updated
# Then ok
# @ignore
# Scenario: The feedback dialog says success or failure
# Then ok