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/instances/navigation.feature

59 lines
2.0 KiB
Gherkin
Raw Normal View History

ui: Rename a model attribute to not be overwritten by ember-data (#9524) * Rename a model attr to not be overwritten by ember-data * Make sure we can click on the instances * Make sure we can click back to the preevious page, not root * Add a forwards/back/forwards navigation test for service instances * Rename a model attr to not be overwritten by ember-data Co-authored-by: John Cowen <jcowen@hashicorp.com>
2021-01-12 14:53:21 +00:00
@setupApplicationTest
Feature: dc / services / instances / navigation
Background:
Given 1 datacenter model with the value "dc-1"
And 1 proxy model from yaml
---
ServiceName: service-0-proxy
Node: node-0
ServiceID: service-a-proxy
---
And 3 instance models from yaml
---
- Service:
ui: Ensure proxy instance health is taken into account in Service Instance Listings (#12279) We noticed that the Service Instance listing on both Node and Service views where not taking into account proxy instance health. This fixes that up so that the small health check information in each Service Instance row includes the proxy instances health checks when displaying Service Instance health (afterall if the proxy instance is unhealthy then so is the service instance that it should be proxying) * Refactor Consul::InstanceChecks with docs * Add to-hash helper, which will return an object keyed by a prop * Stop using/relying on ember-data type things, just use a hash lookup * For the moment add an equivalent "just give me proxies" model prop * Start stitching things together, this one requires an extra HTTP request ..previously we weren't even requesting proxies instances here * Finish up the stitching * Document Consul::ServiceInstance::List while I'm here * Fix up navigation mocks Name > Service
2022-02-10 15:28:26 +00:00
Service: service-0
ui: Rename a model attribute to not be overwritten by ember-data (#9524) * Rename a model attr to not be overwritten by ember-data * Make sure we can click on the instances * Make sure we can click back to the preevious page, not root * Add a forwards/back/forwards navigation test for service instances * Rename a model attr to not be overwritten by ember-data Co-authored-by: John Cowen <jcowen@hashicorp.com>
2021-01-12 14:53:21 +00:00
ID: service-a
Node:
Node: node-0
Checks:
- Status: critical
- Service:
ui: Ensure proxy instance health is taken into account in Service Instance Listings (#12279) We noticed that the Service Instance listing on both Node and Service views where not taking into account proxy instance health. This fixes that up so that the small health check information in each Service Instance row includes the proxy instances health checks when displaying Service Instance health (afterall if the proxy instance is unhealthy then so is the service instance that it should be proxying) * Refactor Consul::InstanceChecks with docs * Add to-hash helper, which will return an object keyed by a prop * Stop using/relying on ember-data type things, just use a hash lookup * For the moment add an equivalent "just give me proxies" model prop * Start stitching things together, this one requires an extra HTTP request ..previously we weren't even requesting proxies instances here * Finish up the stitching * Document Consul::ServiceInstance::List while I'm here * Fix up navigation mocks Name > Service
2022-02-10 15:28:26 +00:00
Service: service-0
ui: Rename a model attribute to not be overwritten by ember-data (#9524) * Rename a model attr to not be overwritten by ember-data * Make sure we can click on the instances * Make sure we can click back to the preevious page, not root * Add a forwards/back/forwards navigation test for service instances * Rename a model attr to not be overwritten by ember-data Co-authored-by: John Cowen <jcowen@hashicorp.com>
2021-01-12 14:53:21 +00:00
ID: service-b
Node:
Node: node-0
Checks:
- Status: passing
# A listing of instances from 2 services would never happen in consul but
# this satisfies our mocking needs for the moment, until we have a 'And 1
# proxy on request.0 from yaml', 'And 1 proxy on request.1 from yaml' or
# similar
- Service:
ui: Ensure proxy instance health is taken into account in Service Instance Listings (#12279) We noticed that the Service Instance listing on both Node and Service views where not taking into account proxy instance health. This fixes that up so that the small health check information in each Service Instance row includes the proxy instances health checks when displaying Service Instance health (afterall if the proxy instance is unhealthy then so is the service instance that it should be proxying) * Refactor Consul::InstanceChecks with docs * Add to-hash helper, which will return an object keyed by a prop * Stop using/relying on ember-data type things, just use a hash lookup * For the moment add an equivalent "just give me proxies" model prop * Start stitching things together, this one requires an extra HTTP request ..previously we weren't even requesting proxies instances here * Finish up the stitching * Document Consul::ServiceInstance::List while I'm here * Fix up navigation mocks Name > Service
2022-02-10 15:28:26 +00:00
Service: service-0-proxy
ui: Rename a model attribute to not be overwritten by ember-data (#9524) * Rename a model attr to not be overwritten by ember-data * Make sure we can click on the instances * Make sure we can click back to the preevious page, not root * Add a forwards/back/forwards navigation test for service instances * Rename a model attr to not be overwritten by ember-data Co-authored-by: John Cowen <jcowen@hashicorp.com>
2021-01-12 14:53:21 +00:00
ID: service-a-proxy
Node:
Node: node-0
Checks:
- Status: passing
---
Scenario: Clicking a instance in the listing and back again
When I visit the service page for yaml
---
dc: dc-1
service: service-0
---
And I click instances on the tabs
Then the url should be /dc-1/services/service-0/instances
Then I see 3 instance models
When I click instance on the instances component
Then a GET request was made to "/v1/catalog/connect/service-0?dc=dc-1&ns=@namespace"
Then a GET request was made to "/v1/health/service/service-0-proxy?dc=dc-1&ns=@namespace"
Then the url should be /dc-1/services/service-0/instances/node-0/service-a/health-checks
And I click "[data-test-back]"
Then the url should be /dc-1/services/service-0/topology
And I click instances on the tabs
When I click instance on the instances component
Then a GET request was made to "/v1/catalog/connect/service-0?dc=dc-1&ns=@namespace"
Then a GET request was made to "/v1/health/service/service-0-proxy?dc=dc-1&ns=@namespace"
Then the url should be /dc-1/services/service-0/instances/node-0/service-a/health-checks