b279f23372
1. Addition of external source icons for services marked as such. 2. New %with-tooltip css component (wip) 3. New 'no healthcheck' icon as external sources might not have healthchecks, also minus icon on node cards in the service detail view 4. If a service doesn't have healthchecks, we use the [Services] tabs as the default instead of the [Health Checks] tab in the Service detail page. 5. `css-var` helper. The idea here is that it will eventually be replaced with pure css custom properties instead of having to use JS. It would be nice to be able to build the css variables into the JS at build time (you'd probably still want to specify in config which variables you wanted available in JS), but that's possible future work. Lastly there is probably a tiny bit more testing edits here than usual, I noticed that there was an area where the dynamic mocking wasn't happening, it was just using the mocks from consul-api-double, the mocks I was 'dynamically' setting happened to be the same as the ones in consul-api-double. I've fixed this here also but it wasn't effecting anything until actually made certain values dynamic.
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
|