consul/ui-v2/tests/acceptance
John Cowen 5debc74fa2 ui: Enable blocking queries by default (#6194)
-Enable blocking queries by default
-Change assertion to check for the last PUT request, not just any request for session destruction from a node page.

Since we've now turned on blocking queries by default this means that a
second GET request is made after the PUT request that we are asserting
for but before the assertion itself, this meant the assertion failed. We
double checked this by turning off blocking queries for this test using

```
And settings from yaml
---
consul:client:
  blocking: 0
---
```

which made the test pass again.

As moving forwards blocking queries will be on by default, we didn't
want to disable blocking queries for this test, so we now assert the
last PUT request specifically. This means we continue to assert that the
session has been destroyed but means we don't get into problems of
ordering of requests here
2019-09-04 08:35:14 +00:00
..
components Fix text and add feature test for copy button (#5958) 2019-06-27 10:01:30 +01:00
dc ui: Enable blocking queries by default (#6194) 2019-09-04 08:35:14 +00:00
settings UI: New ACLs (#4789) 2018-10-19 08:45:05 -07:00
steps ui: [Bugfix] - Sticky KV Sessions (#6166) 2019-09-04 08:35:13 +00:00
deleting.feature UI: ACL Roles (#5635) 2019-05-01 18:22:37 +00:00
index-forwarding.feature WIP: Feature/acceptance tests 2018-06-12 11:24:35 +01:00
page-navigation.feature UI: ACL Roles (#5635) 2019-05-01 18:22:37 +00:00
startup.feature Reset `<html class>` after every test, back to its original static value 2018-06-25 12:11:01 +01:00
submit-blank.feature Add some low hanging intention tests, basically add intentions to others 2018-07-04 13:21:30 +01:00
token-header.feature UI: Catch 500 error on token endpoint and revert to legacy tokens (#4874) 2018-11-02 14:44:36 +00:00