c4f4f4e3c6
* Adds an acceptance test for hiding Blocking Queries * Creates a new scenario - If a user adds CONSUL_UI_DISABLE_REALTIME to localStorage, the Blocking Queries section is hidden. * Updates page assertion to accept functions and booleans as properties * ui: Fix "don't see" step to watch for the different pageObject error ember-cli-page object seems to throw a an error with a different message depending on how you call a function: currentPage()[property]() // message = 'Element not found' const prop = currentPage()[property]; prop() // message = 'Something about destructuring' This changes the step/test/assertion to ensure we check for both types of errors Co-authored-by: John Cowen <johncowen@users.noreply.github.com>
24 lines
803 B
Gherkin
24 lines
803 B
Gherkin
@setupApplicationTest
|
|
@notNamespaceable
|
|
|
|
Feature: settings / show: Show Settings Page
|
|
Scenario: I see the Blocking queries
|
|
Given 1 datacenter model with the value "datacenter"
|
|
When I visit the settings page
|
|
Then the url should be /setting
|
|
And the title should be "Settings - Consul"
|
|
And I see blockingQueries
|
|
Scenario: Setting CONSUL_UI_DISABLE_REALTIME hides Blocking Queries
|
|
Given 1 datacenter model with the value "datacenter"
|
|
And settings from yaml
|
|
---
|
|
CONSUL_UI_DISABLE_REALTIME: 1
|
|
---
|
|
Then I have settings like yaml
|
|
---
|
|
CONSUL_UI_DISABLE_REALTIME: "1"
|
|
---
|
|
When I visit the settings page
|
|
Then the url should be /setting
|
|
And the title should be "Settings - Consul"
|
|
And I don't see blockingQueries |