958991db94
* Create ConsulServiceInstanceList with styling and test * Implement ConsulServiceInstanceList to Service Detail page * Implement ConsulExternalSource to Services Show page header * Update services/show page object * Update the styling of CompositeRow * Refactor ConsulServiceList component and styling * Update ConsulExternalSource to say 'Registered via...' * Upgrade consul-api-double to patch 2.14.1 * Fix up tests to not use Kind in service models * Update ListCollection with clickFirstAnchor action * Add $typo-size-450 to typography base variables
38 lines
1.2 KiB
Gherkin
38 lines
1.2 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / error: Recovering from a dc 500 error
|
|
Background:
|
|
Given 2 datacenter models from yaml
|
|
---
|
|
- dc-1
|
|
- dc-500
|
|
---
|
|
And 6 service models from yaml
|
|
---
|
|
- Name: Service-0
|
|
- Name: Service-0-proxy
|
|
Kind: 'connect-proxy'
|
|
- Name: Service-1
|
|
- Name: Service-1-proxy
|
|
Kind: 'connect-proxy'
|
|
- Name: Service-2
|
|
- Name: Service-2-proxy
|
|
Kind: 'connect-proxy'
|
|
---
|
|
And the url "/v1/internal/ui/services" responds with a 500 status
|
|
When I visit the services page for yaml
|
|
---
|
|
dc: dc-500
|
|
---
|
|
Then the url should be /dc-500/services
|
|
And the title should be "Consul"
|
|
Then I see the text "500 (The backend responded with an error)" in "[data-test-error]"
|
|
Scenario: Clicking the back to root button
|
|
Given the url "/v1/internal/ui/services" responds with a 200 status
|
|
When I click home
|
|
Then I see 3 service models
|
|
Scenario: Choosing a different dc from the dc menu
|
|
Given the url "/v1/internal/ui/services" responds with a 200 status
|
|
When I click dc on the navigation
|
|
And I click dcs.0.name
|
|
Then I see 3 service models
|