[Security Solution] Re-enable a skipped url state e2e test (#152075)

**Relates to:** https://github.com/elastic/kibana/pull/151244

## Summary

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

## Details

Investigation has shown that https://github.com/elastic/kibana/pull/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.
This commit is contained in:
Maxim Palenov 2023-03-01 10:04:31 +01:00 committed by GitHub
parent b867701ab8
commit 5514f93fc8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -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"');
});