consul/ui/packages/consul-ui/tests/acceptance/dc/services/index.feature

168 lines
4.3 KiB
Gherkin
Raw Normal View History

2018-05-11 12:47:21 +00:00
@setupApplicationTest
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
Feature: dc / services / index: List Services
Scenario: Viewing the service list page with services
2018-05-11 12:47:21 +00:00
Given 1 datacenter model with the value "dc-1"
And 10 service models from yaml
---
- Name: Service-0
ExternalSources:
- consul
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 10
Kind: ~
- Name: Service-0-proxy
Kind: 'connect-proxy'
- Name: Service-1
ExternalSources:
- nomad
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 9
Kind: ~
- Name: Service-1-proxy
Kind: 'connect-proxy'
- Name: Service-2
ExternalSources:
- terraform
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 8
Kind: ~
- Name: Service-2-proxy
Kind: 'connect-proxy'
- Name: Service-3
ExternalSources:
- kubernetes
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 7
Kind: ~
- Name: Service-3-proxy
Kind: 'connect-proxy'
- Name: Service-4
ExternalSources:
- aws
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 6
Kind: ~
- Name: Service-4-proxy
Kind: 'connect-proxy'
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 5
---
2018-05-11 12:47:21 +00:00
When I visit the services page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/services
And the title should be "Services - Consul"
Then I see 5 service models
And I see externalSource on the services like yaml
---
- consul
- nomad
- terraform
- kubernetes
- aws
---
Scenario: Viewing the service list page with gateways
Given 1 datacenter model with the value "dc-1"
And 3 service models from yaml
---
- Name: Service-0-proxy
Kind: 'connect-proxy'
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 3
- Name: Service-1-ingress-gateway
Kind: 'ingress-gateway'
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 2
- Name: Service-2-terminating-gateway
Kind: 'terminating-gateway'
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 1
---
When I visit the services page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/services
And the title should be "Services - Consul"
Then I see 2 service models
And I see kind on the services like yaml
---
- ingress-gateway
- terminating-gateway
---
Scenario: View a Service in mesh
Given 1 datacenter model with the value "dc-1"
And 3 service models from yaml
---
- Name: Service-0
Kind: ~
ConnectedWithProxy: true
ConnectedWithGateway: true
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 2
- Name: Service-0-proxy
Kind: connect-proxy
- Name: Service-1
Kind: ~
ConnectedWithProxy: false
ConnectedWithGateway: false
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 1
---
When I visit the services page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/services
And the title should be "Services - Consul"
Then I see 2 service models
And I see mesh on the services.0
And I don't see mesh on the services.1
Scenario: View a Service's Associated Service count
Given 1 datacenter model with the value "dc-1"
And 3 service models from yaml
---
- Name: Service-0
Kind: ~
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 2
- Name: Service-0-proxy
Kind: connect-proxy
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 1
- Name: Service-1
Kind: 'ingress-gateway'
ChecksPassing: 0
ChecksWarning: 0
ChecksCritical: 1
GatewayConfig:
AssociatedServiceCount: 345
---
When I visit the services page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/services
And the title should be "Services - Consul"
Then I see 2 service models
And I don't see associatedServiceCount on the services.0
And I see associatedServiceCount on the services.1