Skip to content

Commit

Permalink
[Security Solution] Re-enable a skipped url state e2e test (elastic#1…
Browse files Browse the repository at this point in the history
…52075)

**Relates to:** elastic#151244

## Summary

Re-enable `Do not clears kql when navigating to a new page` url state e2e test.

## Details

Investigation has shown that elastic#150787 lead to breaking this test. While it's not clear from the EUI upgrade PR itself the cause lays under the hood. It fixes retrieving the state (current KQL) from the url. As the test visits the page with the saved KQL which is properly restored the next `kqlSearch()` command types the same KQL in the query bar leading to invalid KQL and broken test eventually. For some reason the KQL wasn't able to restore on this page while it's not an issue anymore I removed `kqlSearch()` command and fixed the test this way.
  • Loading branch information
maximpn authored Mar 1, 2023
1 parent b867701 commit 5514f93
Showing 1 changed file with 1 addition and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -274,10 +274,8 @@ describe('url state', () => {
);
});

// Failing on `main`, skipping for now, to be addressed by security-detection-rules-area
it.skip('Do not clears kql when navigating to a new page', () => {
it('Do not clears kql when navigating to a new page', () => {
visitWithoutDateRange(ABSOLUTE_DATE_RANGE.urlKqlHostsHosts);
kqlSearch('source.ip: "10.142.0.9"{enter}');
navigateFromHeaderTo(NETWORK);
cy.get(KQL_INPUT).should('have.text', 'source.ip: "10.142.0.9"');
});
Expand Down

0 comments on commit 5514f93

Please sign in to comment.