luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-consul/ui/packages/consul-ui/tests/acceptance/dc/services/show/topology.feature

71 lines
2.1 KiB
Gherkin
Raw Normal View History

ui: Topology intention saving improvements (#9513) * ui: Keep track of existing intentions and use those to save changes Previously we risked overwriting existing data in an intention if we tried to save an intention without having loaded it first, for example Description and Metadata would have been overwritten. This change loads in all the intentions for an origin service so we can pick off the one we need to save and change to ensure that we don't overwrite any existing data.
2021-01-19 15:40:39 +00:00
@setupApplicationTest
Feature: dc / services / show / topology: Intention Create
Background:
Given 1 datacenter model with the value "datacenter"
ui: Add some acceptance testing around the Metrics graph (#9785) * Add a way to set the local datacenter * Amend step so we can positively and negatively look for elements * Add a data-test selector so we can get to the topology series graph * Add a couple of tests to verify the series graph shows/doesn't show
2021-02-18 18:31:49 +00:00
And the local datacenter is "datacenter"
ui: Topology intention saving improvements (#9513) * ui: Keep track of existing intentions and use those to save changes Previously we risked overwriting existing data in an intention if we tried to save an intention without having loaded it first, for example Description and Metadata would have been overwritten. This change loads in all the intentions for an origin service so we can pick off the one we need to save and change to ensure that we don't overwrite any existing data.
2021-01-19 15:40:39 +00:00
And 1 intention model from yaml
---
SourceNS: default
SourceName: web
DestinationNS: default
DestinationName: db
ID: intention-id
---
And 1 node model
And 1 service model from yaml
---
- Service:
Name: web
Kind: ~
---
And 1 topology model from yaml
---
Downstreams: []
Upstreams:
- Name: db
Namespace: default
Datacenter: datacenter
Intention: {}
---
ui: Add some acceptance testing around the Metrics graph (#9785) * Add a way to set the local datacenter * Amend step so we can positively and negatively look for elements * Add a data-test selector so we can get to the topology series graph * Add a couple of tests to verify the series graph shows/doesn't show
2021-02-18 18:31:49 +00:00
Scenario: Metrics is not enabled with prometheus provider
ui: Topology intention saving improvements (#9513) * ui: Keep track of existing intentions and use those to save changes Previously we risked overwriting existing data in an intention if we tried to save an intention without having loaded it first, for example Description and Metadata would have been overwritten. This change loads in all the intentions for an origin service so we can pick off the one we need to save and change to ensure that we don't overwrite any existing data.
2021-01-19 15:40:39 +00:00
When I visit the service page for yaml
---
dc: datacenter
service: web
---
ui: Add some acceptance testing around the Metrics graph (#9785) * Add a way to set the local datacenter * Amend step so we can positively and negatively look for elements * Add a data-test selector so we can get to the topology series graph * Add a couple of tests to verify the series graph shows/doesn't show
2021-02-18 18:31:49 +00:00
And I don't see the "[data-test-sparkline]" element
Scenario: Metrics is enabled with prometheus provider
Given 1 datacenter model with the value "datacenter"
And the local datacenter is "datacenter"
And ui_config from yaml
---
metrics_proxy_enabled: true
metrics_provider: 'prometheus'
---
When I visit the service page for yaml
---
dc: datacenter
service: web
---
And I see the "[data-test-sparkline]" element
ui: Topology intention saving improvements (#9513) * ui: Keep track of existing intentions and use those to save changes Previously we risked overwriting existing data in an intention if we tried to save an intention without having loaded it first, for example Description and Metadata would have been overwritten. This change loads in all the intentions for an origin service so we can pick off the one we need to save and change to ensure that we don't overwrite any existing data.
2021-01-19 15:40:39 +00:00
Scenario: Allow a connection between service and upstream by saving an intention
ui: Add some acceptance testing around the Metrics graph (#9785) * Add a way to set the local datacenter * Amend step so we can positively and negatively look for elements * Add a data-test selector so we can get to the topology series graph * Add a couple of tests to verify the series graph shows/doesn't show
2021-02-18 18:31:49 +00:00
When I visit the service page for yaml
---
dc: datacenter
service: web
---
ui: Topology intention saving improvements (#9513) * ui: Keep track of existing intentions and use those to save changes Previously we risked overwriting existing data in an intention if we tried to save an intention without having loaded it first, for example Description and Metadata would have been overwritten. This change loads in all the intentions for an origin service so we can pick off the one we need to save and change to ensure that we don't overwrite any existing data.
2021-01-19 15:40:39 +00:00
When I click ".consul-topology-metrics [data-test-action]"
And I click ".consul-topology-metrics [data-test-confirm]"
And "[data-notification]" has the "success" class
Scenario: There was an error saving the intention
Given the url "/v1/connect/intentions/exact?source=default%2Fweb&destination=default%2Fdb&dc=datacenter" responds with a 500 status
ui: Add some acceptance testing around the Metrics graph (#9785) * Add a way to set the local datacenter * Amend step so we can positively and negatively look for elements * Add a data-test selector so we can get to the topology series graph * Add a couple of tests to verify the series graph shows/doesn't show
2021-02-18 18:31:49 +00:00
When I visit the service page for yaml
---
dc: datacenter
service: web
---
ui: Topology intention saving improvements (#9513) * ui: Keep track of existing intentions and use those to save changes Previously we risked overwriting existing data in an intention if we tried to save an intention without having loaded it first, for example Description and Metadata would have been overwritten. This change loads in all the intentions for an origin service so we can pick off the one we need to save and change to ensure that we don't overwrite any existing data.
2021-01-19 15:40:39 +00:00
When I click ".consul-topology-metrics [data-test-action]"
And I click ".consul-topology-metrics [data-test-confirm]"
And "[data-notification]" has the "error" class