consul/ui-v2/tests/acceptance/dc/nodes/sessions/list.feature

@setupApplicationTest
Feature: dc / nodes / sessions / list: List Lock Sessions
  In order to get information regarding lock sessions
  As a user
  I should be able to see a listing of lock sessions with necessary information under the lock sessions tab for a node
  Scenario: Given 2 session with string TTLs
    Given 1 datacenter model with the value "dc1"
    And 1 node model from yaml
    ---
    ID: node-0
    ---
    And 2 session models from yaml
    ---
    - TTL: 30s
    - TTL: 60m
    ---
    When I visit the node page for yaml
    ---
      dc: dc1
      node: node-0
    ---
    And I click lockSessions on the tabs
    Then I see lockSessionsIsSelected on the tabs
    Then I see TTL on the sessions like yaml
    ---
    - 30s
    - 60m
    ---
Add a failing test to show that lock session TTL's are not shown 2018-06-19 14:25:56 +00:00			`@setupApplicationTest`
Lock Session invalidation acceptance test 2018-07-04 12:41:44 +00:00			`Feature: dc / nodes / sessions / list: List Lock Sessions`
Add a failing test to show that lock session TTL's are not shown 2018-06-19 14:25:56 +00:00			`In order to get information regarding lock sessions`
			`As a user`
			`I should be able to see a listing of lock sessions with necessary information under the lock sessions tab for a node`
			`Scenario: Given 2 session with string TTLs`
			`Given 1 datacenter model with the value "dc1"`
			`And 1 node model from yaml`
			`---`
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			`ID: node-0`
Add a failing test to show that lock session TTL's are not shown 2018-06-19 14:25:56 +00:00			`---`
			`And 2 session models from yaml`
			`---`
			`- TTL: 30s`
			`- TTL: 60m`
			`---`
			`When I visit the node page for yaml`
			`---`
			`dc: dc1`
			`node: node-0`
			`---`
			`And I click lockSessions on the tabs`
			`Then I see lockSessionsIsSelected on the tabs`
			`Then I see TTL on the sessions like yaml`
			`---`
			`- 30s`
			`- 60m`
			`---`