consul/ui-v2/tests/acceptance/dc/acls/roles/as-many/add-existing.feature

49 lines
1.4 KiB
Gherkin
Raw Normal View History

@setupApplicationTest
Feature: dc / acls / roles / as many / add existing: Add existing
Scenario:
Given 1 datacenter model with the value "datacenter"
And 1 token model from yaml
---
AccessorID: key
Description: The Description
Roles: ~
---
And 2 role models from yaml
---
- ID: role-1
Name: Role 1
- ID: role-2
Name: Role 2
---
When I visit the token page for yaml
---
dc: datacenter
token: key
---
Then the url should be /datacenter/acls/tokens/key
And I click "#roles .ember-power-select-trigger"
And I click ".ember-power-select-option:first-child"
And I see 1 role model on the roles component
And I click "#roles .ember-power-select-trigger"
And I click ".ember-power-select-option:nth-child(1)"
And I see 2 role models on the roles component
Then I fill in with yaml
---
Description: The Description
---
And I submit
ui: Acceptance test improvements to prepare for more NS tests (#6980) * 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
2020-01-24 12:26:28 +00:00
Then a PUT request was made to "/v1/acl/token/key?dc=datacenter" from yaml
---
body:
Namespace: @namespace
Description: The Description
Roles:
- ID: role-1
Name: Role 1
- ID: role-2
Name: Role 2
---
Then the url should be /datacenter/acls/tokens
And "[data-notification]" has the "notification-update" class
And "[data-notification]" has the "success" class