open-consul/ui-v2/tests/acceptance/dc/acls/roles/create.feature
John Cowen 5b7a48e273
ui: oss don't ever POST/PUT Namespaces when writing data (#7238)
* ui: Ensure we use nonEmptySet everywhere where we add Namespace

We missed a coupld of places where we use the noEmptySet function, which
will only perform the set if the specified property is non-empty.

Currently we aren't certain there is a place in OSS where a Namespace
can make its way down via the API and endup being PUT/POSTed back out
again when saved. If this did ever happen we would assume it would be
the default namespace, but we add an extra check here to ensure we never
PUT/POST the Namespace property if Namespaces are disabled.

* ui: Add step/assertion for assert if a property is NOT set in the body

* ui: Improve updated/create acc testing for policy/token/roles:

Including making sure a Namespace property is never sent through if you
are running without namespace support
2020-02-07 15:50:50 +00:00

52 lines
1.6 KiB
Gherkin

@setupApplicationTest
Feature: dc / acls / roles / create
Background:
Given 1 datacenter model with the value "datacenter"
When I visit the role page for yaml
---
dc: datacenter
---
Scenario: Visiting the page without error and the title is correct
Then the url should be /datacenter/acls/roles/create
And the title should be "New Role - Consul"
Scenario: Creating a simple ACL role with description [Description]
Then I fill in the role form with yaml
---
Name: my-role
Description: [Description]
---
And I submit
Then a PUT request was made to "/v1/acl/role?dc=datacenter" from yaml
---
body:
Namespace: @namespace
Name: my-role
Description: [Description]
---
Then the url should be /datacenter/acls/roles
And "[data-notification]" has the "notification-create" class
And "[data-notification]" has the "success" class
Where:
---------------------------
| Description |
| description |
| description with spaces |
---------------------------
@notNamespaceable
Scenario: Creating a simple ACL role when Namespaces are disabled does not send Namespace
Then I fill in the role form with yaml
---
Name: my-role
Description: Description
---
And I submit
Then a PUT request was made to "/v1/acl/role?dc=datacenter" without properties from yaml
---
- Namespace
---
Then the url should be /datacenter/acls/roles
And "[data-notification]" has the "notification-create" class
And "[data-notification]" has the "success" class