mirror of
https://github.com/status-im/consul.git
synced 2025-02-02 08:56:43 +00:00
5debc74fa2
-Enable blocking queries by default -Change assertion to check for the last PUT request, not just any request for session destruction from a node page. Since we've now turned on blocking queries by default this means that a second GET request is made after the PUT request that we are asserting for but before the assertion itself, this meant the assertion failed. We double checked this by turning off blocking queries for this test using ``` And settings from yaml --- consul:client: blocking: 0 --- ``` which made the test pass again. As moving forwards blocking queries will be on by default, we didn't want to disable blocking queries for this test, so we now assert the last PUT request specifically. This means we continue to assert that the session has been destroyed but means we don't get into problems of ordering of requests here
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 the last PUT request was 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
|