open-consul/ui-v2/tests/acceptance/dc/services/show.feature

@setupApplicationTest
Feature: dc / services / show: Show Service
  Scenario: Given a service with an external source, the logo is displayed
    Given 1 datacenter model with the value "dc1"
    And 1 node models
    And 1 service model from yaml
    ---
    - Service:
        Tags: ['Tag1', 'Tag2']
        Meta:
          external-source: consul
    ---
    When I visit the service page for yaml
    ---
      dc: dc1
      service: service-0
    ---
    Then I see externalSource like "consul"
  Scenario: Given a service with an 'unsupported' external source, there is no logo
    Given 1 datacenter model with the value "dc1"
    And 1 node models
    And 1 service model from yaml
    ---
    - Service:
        Tags: ['Tag1', 'Tag2']
        Meta:
          external-source: 'not-supported'
    ---
    When I visit the service page for yaml
    ---
      dc: dc1
      service: service-0
    ---
    Then I don't see externalSource
  Scenario: Given various services with various tags, all tags are displayed
    Given 1 datacenter model with the value "dc1"
    And 3 node models
    And 1 service model from yaml
    ---
    - Service:
        Tags: ['Tag1', 'Tag2']
    - Service:
        Tags: ['Tag3', 'Tag1']
    - Service:
        Tags: ['Tag2', 'Tag3']
    ---
    When I visit the service page for yaml
    ---
      dc: dc1
      service: service-0
    ---
    Then I see the text "Tag1" in "[data-test-tags] span:nth-child(1)"
    Then I see the text "Tag2" in "[data-test-tags] span:nth-child(2)"
    Then I see the text "Tag3" in "[data-test-tags] span:nth-child(3)"
  Scenario: Given various services the various nodes on their instances are displayed
    Given 1 datacenter model with the value "dc1"
    And 3 node models
    And 1 service model from yaml
    ---
    - Checks:
        - Status: passing
      Service:
        ID: passing-service-8080
        Port: 8080
        Address: 1.1.1.1
      Node:
        Address: 1.2.2.2
    - Service:
        ID: service-8000
        Port: 8000
        Address: 2.2.2.2
      Node:
        Address: 2.3.3.3
    - Service:
        ID: service-8888
        Port: 8888
        Address: 3.3.3.3
      Node:
        Address: 3.4.4.4
    ---
    When I visit the service page for yaml
    ---
      dc: dc1
      service: service-0
    ---
    Then I see address on the instances like yaml
    ---
      - "1.1.1.1:8080"
      - "2.2.2.2:8000"
      - "3.3.3.3:8888"
    ---
Ensure all tags for a service are listed on the service detail page 2018-06-18 14:38:52 +00:00			`@setupApplicationTest`
			`Feature: dc / services / show: Show Service`
UI: External Source markers (#4640) 1. Addition of external source icons for services marked as such. 2. New %with-tooltip css component (wip) 3. New 'no healthcheck' icon as external sources might not have healthchecks, also minus icon on node cards in the service detail view 4. If a service doesn't have healthchecks, we use the [Services] tabs as the default instead of the [Health Checks] tab in the Service detail page. 5. `css-var` helper. The idea here is that it will eventually be replaced with pure css custom properties instead of having to use JS. It would be nice to be able to build the css variables into the JS at build time (you'd probably still want to specify in config which variables you wanted available in JS), but that's possible future work. Lastly there is probably a tiny bit more testing edits here than usual, I noticed that there was an area where the dynamic mocking wasn't happening, it was just using the mocks from consul-api-double, the mocks I was 'dynamically' setting happened to be the same as the ones in consul-api-double. I've fixed this here also but it wasn't effecting anything until actually made certain values dynamic. 2018-09-12 19:23:39 +00:00			`Scenario: Given a service with an external source, the logo is displayed`
			`Given 1 datacenter model with the value "dc1"`
			`And 1 node models`
			`And 1 service model from yaml`
			`---`
			`- Service:`
			`Tags: ['Tag1', 'Tag2']`
			`Meta:`
			`external-source: consul`
			`---`
			`When I visit the service page for yaml`
			`---`
			`dc: dc1`
			`service: service-0`
			`---`
			`Then I see externalSource like "consul"`
ui: If a service has no external-source, don't show the icon (#4996) 2018-11-26 17:34:00 +00:00			`Scenario: Given a service with an 'unsupported' external source, there is no logo`
			`Given 1 datacenter model with the value "dc1"`
			`And 1 node models`
			`And 1 service model from yaml`
			`---`
			`- Service:`
			`Tags: ['Tag1', 'Tag2']`
			`Meta:`
			`external-source: 'not-supported'`
			`---`
			`When I visit the service page for yaml`
			`---`
			`dc: dc1`
			`service: service-0`
			`---`
			`Then I don't see externalSource`
Add port the service is running on for each node in the service view 2018-06-20 12:08:59 +00:00			`Scenario: Given various services with various tags, all tags are displayed`
Ensure all tags for a service are listed on the service detail page 2018-06-18 14:38:52 +00:00			`Given 1 datacenter model with the value "dc1"`
			`And 3 node models`
			`And 1 service model from yaml`
			`---`
			`- Service:`
			`Tags: ['Tag1', 'Tag2']`
			`- Service:`
			`Tags: ['Tag3', 'Tag1']`
			`- Service:`
			`Tags: ['Tag2', 'Tag3']`
			`---`
			`When I visit the service page for yaml`
			`---`
			`dc: dc1`
			`service: service-0`
			`---`
Make sure the updated tag view doesn't break the tests 2018-06-20 14:26:22 +00:00			`Then I see the text "Tag1" in "[data-test-tags] span:nth-child(1)"`
			`Then I see the text "Tag2" in "[data-test-tags] span:nth-child(2)"`
			`Then I see the text "Tag3" in "[data-test-tags] span:nth-child(3)"`
UI: Service Instances (#5326) This gives more prominence to 'Service Instances' as opposed to 'Services'. It also begins to surface Connect related 'nouns' such as 'Proxies' and 'Upstreams' and begins to interconnect them giving more visibility to operators. Various smaller changes: 1. Move healthcheck-status component to healthcheck-output 2. Create a new healthcheck-status component for showing the number of checks plus its icon 3. Create a new healthcheck-info component to group multiple statuses plus a different view if there are no checks 4. Componentize tag-list 2019-02-21 13:10:53 +00:00			`Scenario: Given various services the various nodes on their instances are displayed`
Add port the service is running on for each node in the service view 2018-06-20 12:08:59 +00:00			`Given 1 datacenter model with the value "dc1"`
			`And 3 node models`
			`And 1 service model from yaml`
			`---`
			`- Checks:`
			`- Status: passing`
			`Service:`
Acceptance tests to search/look for service id's 2018-07-12 12:35:33 +00:00			`ID: passing-service-8080`
Add port the service is running on for each node in the service view 2018-06-20 12:08:59 +00:00			`Port: 8080`
			`Address: 1.1.1.1`
Make the tests break by switching to a Service.IP 2018-07-18 12:35:57 +00:00			`Node:`
			`Address: 1.2.2.2`
Add port the service is running on for each node in the service view 2018-06-20 12:08:59 +00:00			`- Service:`
Acceptance tests to search/look for service id's 2018-07-12 12:35:33 +00:00			`ID: service-8000`
Add port the service is running on for each node in the service view 2018-06-20 12:08:59 +00:00			`Port: 8000`
			`Address: 2.2.2.2`
Make the tests break by switching to a Service.IP 2018-07-18 12:35:57 +00:00			`Node:`
			`Address: 2.3.3.3`
Add port the service is running on for each node in the service view 2018-06-20 12:08:59 +00:00			`- Service:`
Acceptance tests to search/look for service id's 2018-07-12 12:35:33 +00:00			`ID: service-8888`
Add port the service is running on for each node in the service view 2018-06-20 12:08:59 +00:00			`Port: 8888`
			`Address: 3.3.3.3`
Make the tests break by switching to a Service.IP 2018-07-18 12:35:57 +00:00			`Node:`
			`Address: 3.4.4.4`
Add port the service is running on for each node in the service view 2018-06-20 12:08:59 +00:00			`---`
			`When I visit the service page for yaml`
			`---`
			`dc: dc1`
			`service: service-0`
			`---`
UI: Service Instances (#5326) This gives more prominence to 'Service Instances' as opposed to 'Services'. It also begins to surface Connect related 'nouns' such as 'Proxies' and 'Upstreams' and begins to interconnect them giving more visibility to operators. Various smaller changes: 1. Move healthcheck-status component to healthcheck-output 2. Create a new healthcheck-status component for showing the number of checks plus its icon 3. Create a new healthcheck-info component to group multiple statuses plus a different view if there are no checks 4. Componentize tag-list 2019-02-21 13:10:53 +00:00			`Then I see address on the instances like yaml`
Add port the service is running on for each node in the service view 2018-06-20 12:08:59 +00:00			`---`
			`- "1.1.1.1:8080"`
			`- "2.2.2.2:8000"`
			`- "3.3.3.3:8888"`
			`---`