fde7ca365a
* ui: Acceptance test improvements to prepare for more NS tests * ui: Namespace acceptance testing (#7005) * Update api-double and consul-api-double for http.body * Adds places where we missed passing the nspace through * Hardcode nspace CRUD to use the default nspace for policies and roles * Alter test helpers to allow us to control nspaces from the outside * Amends to allow tests to account for namespace, move ns from queryParam 1. We decided to move how we pass the namespace value through to the backend when performing write actions (create, update). Previoulsy we were using the queryParam although using the post body is the preferred method to send the Namespace details through to the backend. 2. Other various amends to take into account testing across multiple namespaced scenarios * Enable nspace testing by default * Remove last few occurances of old style http assertions We had informally 'deprecated' our old style of http assertions that relied on the order of http calls (even though that order was not important for the assertion). Following on from our namespace work we removed the majority of the old occrances of these old style assertions. This commit removes the remaining few, and also then cleans up the assertions/http.js file to only include the ones we are using. This reduces our available step count further and prevents any confusion over the usage of the old types and the new types. * ui: Namespace CRUD acceptance tests (#7016) * Upgrade consul-api-double * Add all the things required for testing: 1. edit and index page objects 2. enable CONSUL_NSPACE_COUNT cookie setting 3. enable mutating HTTP response bodies based on URL * Add acceptance test for nspace edit/delete/list and searching
115 lines
3.7 KiB
Gherkin
115 lines
3.7 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / kvs / update: KV Update
|
|
Background:
|
|
Given 1 datacenter model with the value "datacenter"
|
|
Scenario: Update to [Name] change value to [Value]
|
|
And 1 kv model from yaml
|
|
---
|
|
Key: "[Name]"
|
|
---
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
kv: "[Name]"
|
|
---
|
|
Then the url should be /datacenter/kv/[EncodedName]/edit
|
|
# Turn the Code Editor off so we can fill the value easier
|
|
And I click "[name=json]"
|
|
Then I fill in with yaml
|
|
---
|
|
value: [Value]
|
|
---
|
|
And I submit
|
|
Then a PUT request was made to "/v1/kv/[EncodedName]?dc=datacenter&ns=@!namespace" with the body "[Value]"
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Where:
|
|
---------------------------------------------------------
|
|
| Name | EncodedName | Value |
|
|
| key | key | value |
|
|
| #key | %23key | value |
|
|
| key-name | key-name | a value |
|
|
| key name | key%20name | a value |
|
|
| folder/key-name | folder/key-name | a value |
|
|
---------------------------------------------------------
|
|
Scenario: Update to a key change value to ' '
|
|
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
|
|
# Turn the Code Editor off so we can fill the value easier
|
|
And I click "[name=json]"
|
|
Then I fill in with yaml
|
|
---
|
|
value: ' '
|
|
---
|
|
And I submit
|
|
Then a PUT request was made to "/v1/kv/key?dc=datacenter&ns=@!namespace" with the body " "
|
|
Then the url should be /datacenter/kv
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Scenario: Update to a key change value to ''
|
|
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
|
|
# Turn the Code Editor off so we can fill the value easier
|
|
And I click "[name=json]"
|
|
Then I fill in with yaml
|
|
---
|
|
value: ''
|
|
---
|
|
And I submit
|
|
Then a PUT request was made to "/v1/kv/key?dc=datacenter&ns=@!namespace" with no body
|
|
Then the url should be /datacenter/kv
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Scenario: Update to a key when the value is empty
|
|
And 1 kv model from yaml
|
|
---
|
|
Key: key
|
|
Value: ~
|
|
---
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
kv: key
|
|
---
|
|
Then the url should be /datacenter/kv/key/edit
|
|
And I submit
|
|
Then a PUT request was made to "/v1/kv/key?dc=datacenter&ns=@!namespace" with no body
|
|
Then the url should be /datacenter/kv
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Scenario: There was an error saving the key
|
|
When I visit the kv page for yaml
|
|
---
|
|
dc: datacenter
|
|
kv: key
|
|
---
|
|
Then the url should be /datacenter/kv/key/edit
|
|
|
|
Given the url "/v1/kv/key" responds with a 500 status
|
|
And I submit
|
|
Then the url should be /datacenter/kv/key/edit
|
|
Then "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "error" class
|
|
@ignore
|
|
Scenario: KV's with spaces are saved correctly
|
|
Then ok
|
|
@ignore
|
|
Scenario: KV's with returns are saved correctly
|
|
Then ok
|