d1fea9ec0a
* 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.
39 lines
1.5 KiB
Gherkin
39 lines
1.5 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / nodes / sessions / invalidate: Invalidate Lock Sessions
|
|
In order to invalidate a lock session
|
|
As a user
|
|
I should be able to invalidate a lock session by clicking a button and confirming
|
|
Background:
|
|
Given 1 datacenter model with the value "dc1"
|
|
And 1 node model from yaml
|
|
---
|
|
- ID: node-0
|
|
---
|
|
And 2 session models from yaml
|
|
---
|
|
- ID: 7bbbd8bb-fff3-4292-b6e3-cfedd788546a
|
|
- ID: 7ccd0bd7-a5e0-41ae-a33e-ed3793d803b2
|
|
---
|
|
When I visit the node page for yaml
|
|
---
|
|
dc: dc1
|
|
node: node-0
|
|
---
|
|
Then the url should be /dc1/nodes/node-0
|
|
And I click lockSessions on the tabs
|
|
Then I see lockSessionsIsSelected on the tabs
|
|
Scenario: Invalidating the lock session
|
|
And I click delete on the sessions
|
|
And I click confirmDelete on the sessions
|
|
Then a PUT request is made to "/v1/session/destroy/7bbbd8bb-fff3-4292-b6e3-cfedd788546a?dc=dc1"
|
|
Then the url should be /dc1/nodes/node-0
|
|
And "[data-notification]" has the "notification-delete" class
|
|
And "[data-notification]" has the "success" class
|
|
Scenario: Invalidating a lock session and receiving an error
|
|
Given the url "/v1/session/destroy/7bbbd8bb-fff3-4292-b6e3-cfedd788546a?dc=dc1" responds with a 500 status
|
|
And I click delete on the sessions
|
|
And I click confirmDelete on the sessions
|
|
Then the url should be /dc1/nodes/node-0
|
|
And "[data-notification]" has the "notification-delete" class
|
|
And "[data-notification]" has the "error" class
|