455dfe0a1b
* Add model layer support for filtering intentions by service * Add Route, Controller and template for services.show.intentions tab We are still loading the intentions themselves in the parent Route for the moment * Load the intentions in in the parent route for the moment * Temporarily add support for returning to history -1 Once we have an intention form underneath the service/intention tab this will no longer be needed * Add the new tab and enable blocking queries for it * Add some further acceptance testing around intention listings
32 lines
1 KiB
Gherkin
32 lines
1 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / services / intentions: Intentions per service
|
|
Background:
|
|
Given 1 datacenter model with the value "dc1"
|
|
And 1 node models
|
|
And 1 service model from yaml
|
|
---
|
|
- Service:
|
|
Kind: consul
|
|
Name: service-0
|
|
ID: service-0-with-id
|
|
---
|
|
And 3 intention models
|
|
When I visit the service page for yaml
|
|
---
|
|
dc: dc1
|
|
service: service-0
|
|
---
|
|
And the title should be "service-0 - Consul"
|
|
And I see intentions on the tabs
|
|
When I click intentions on the tabs
|
|
And I see intentionsIsSelected on the tabs
|
|
Scenario: I can see intentions
|
|
And I see 3 intention models
|
|
Scenario: I can delete intentions
|
|
And I click actions on the intentions
|
|
And I click delete on the intentions
|
|
And I click confirmDelete on the intentions
|
|
Then a DELETE request was made to "/v1/connect/intentions/ee52203d-989f-4f7a-ab5a-2bef004164ca?dc=dc1"
|
|
And "[data-notification]" has the "notification-delete" class
|
|
And "[data-notification]" has the "success" class
|