mirror of
https://github.com/status-im/consul.git
synced 2025-02-06 10:54:11 +00:00
f3d9565277
This commit uses all our new ways of doing things to Lock Sessions and their interactions with KV and Nodes. This is mostly around are new under-the-hood things, but also I took the opportunity to upgrade some of the CSS to reuse some of our CSS utils that have been made over the past few months (%csv-list and %horizontal-kv-list). Also added (and worked on existing) documentation for Lock Session related components.
33 lines
1.3 KiB
Gherkin
33 lines
1.3 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / kvs / 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 "datacenter"
|
|
And 1 kv model from yaml
|
|
---
|
|
Key: key
|
|
---
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
kv: key
|
|
---
|
|
Then the url should be /datacenter/kv/key/edit
|
|
|
|
Scenario: Invalidating the lock session
|
|
And I click delete on the session
|
|
And I click confirmDelete on the session
|
|
Then a PUT request was made to "/v1/session/destroy/ee52203d-989f-4f7a-ab5a-2bef004164ca?dc=datacenter&ns=@!namespace"
|
|
Then the url should be /datacenter/kv/key/edit
|
|
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/ee52203d-989f-4f7a-ab5a-2bef004164ca?dc=datacenter&ns=@namespace" responds with a 500 status
|
|
And I click delete on the session
|
|
And I click confirmDelete on the session
|
|
Then the url should be /datacenter/kv/key/edit
|
|
And "[data-notification]" has the "notification-delete" class
|
|
And "[data-notification]" has the "error" class
|