mirror of
https://github.com/status-im/consul.git
synced 2025-01-09 13:26:07 +00:00
327aac9fe9
* 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
116 lines
3.5 KiB
Gherkin
116 lines
3.5 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / acls / policies / as many / add new: Add new policy
|
|
Background:
|
|
Given 1 datacenter model with the value "datacenter"
|
|
And 1 [Model] model from yaml
|
|
---
|
|
Policies: ~
|
|
ServiceIdentities: ~
|
|
---
|
|
When I visit the [Model] page for yaml
|
|
---
|
|
dc: datacenter
|
|
[Model]: key
|
|
---
|
|
Then the url should be /datacenter/acls/[Model]s/key
|
|
And I click policies.create
|
|
Scenario: Adding a new policy as a child of [Model]
|
|
Then I fill in the policies.form with yaml
|
|
---
|
|
Name: New-Policy
|
|
Description: New Policy Description
|
|
Rules: key {}
|
|
---
|
|
And I click submit on the policies.form
|
|
Then a PUT request was made to "/v1/acl/policy?dc=datacenter" from yaml
|
|
---
|
|
body:
|
|
Name: New-Policy
|
|
Description: New Policy Description
|
|
Namespace: @namespace
|
|
Rules: key {}
|
|
---
|
|
And I submit
|
|
Then a PUT request was made to "/v1/acl/[Model]/key?dc=datacenter" from yaml
|
|
---
|
|
body:
|
|
Namespace: @namespace
|
|
Policies:
|
|
- ID: ee52203d-989f-4f7a-ab5a-2bef004164ca-1
|
|
Name: New-Policy
|
|
---
|
|
Then the url should be /datacenter/acls/[Model]s
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Where:
|
|
-------------
|
|
| Model |
|
|
| token |
|
|
| role |
|
|
-------------
|
|
Scenario: Adding a new service identity as a child of [Model]
|
|
Then I fill in the policies.form with yaml
|
|
---
|
|
Name: New-Service-Identity
|
|
Description: New Service Identity Description
|
|
---
|
|
And I click serviceIdentity on the policies.form
|
|
And I click submit on the policies.form
|
|
And I submit
|
|
Then a PUT request was made to "/v1/acl/[Model]/key?dc=datacenter" from yaml
|
|
---
|
|
body:
|
|
Namespace: @namespace
|
|
ServiceIdentities:
|
|
- ServiceName: New-Service-Identity
|
|
---
|
|
Then the url should be /datacenter/acls/[Model]s
|
|
And "[data-notification]" has the "notification-update" class
|
|
And "[data-notification]" has the "success" class
|
|
Where:
|
|
-------------
|
|
| Model |
|
|
| token |
|
|
| role |
|
|
-------------
|
|
Scenario: Adding a new policy as a child of [Model] and getting an error
|
|
Given the url "/v1/acl/policy" responds with from yaml
|
|
---
|
|
status: 500
|
|
body: |
|
|
Invalid service policy: acl.ServicePolicy{Name:"service", Policy:"", Sentinel:acl.Sentinel{Code:"", EnforcementLevel:""}, Intentions:""}
|
|
---
|
|
Then I fill in the policies.form with yaml
|
|
---
|
|
Name: New-Policy
|
|
Description: New Policy Description
|
|
Rules: key {}
|
|
---
|
|
And I click submit on the policies.form
|
|
Then a PUT request was made to "/v1/acl/policy?dc=datacenter" with the body from yaml
|
|
---
|
|
Name: New-Policy
|
|
Description: New Policy Description
|
|
Namespace: @namespace
|
|
Rules: key {}
|
|
---
|
|
And I see error on the policies.form.rules like 'Invalid service policy: acl.ServicePolicy{Name:"service", Policy:"", Sentinel:acl.Sentinel{Code:"", EnforcementLevel:""}, Intentions:""}'
|
|
Where:
|
|
-------------
|
|
| Model |
|
|
| token |
|
|
| role |
|
|
-------------
|
|
Scenario: Try to edit the Service Identity using the code editor
|
|
And I click serviceIdentity on the policies.form
|
|
Then I can't fill in the policies.form with yaml
|
|
---
|
|
Rules: key {}
|
|
---
|
|
Where:
|
|
-------------
|
|
| Model |
|
|
| token |
|
|
| role |
|
|
-------------
|