Flaky: Functional testing framework sometimes doesn't navigate

[timroes]

We have found this via the _linked_saved_search test case.

The beginning of the test looks like:

before(async () => {
  await PageObjects.common.navigateToUrl('discover', '');
  await PageObjects.discover.saveSearch(savedSearchName);
});

it('should create a visualization from a saved search', async () => {
  retry.try(async () => {
    // Sometimes navigation to the page fails, so we have this in a retry
    await PageObjects.common.navigateToUrl('visualize', 'new');
    await PageObjects.visualize.waitForVisualizationSelectPage();
  });

This will navigate to discover and save a search. The saveSearch method actually ends with a await testSubjects.exists('saveSearchSuccess', 2000); to wait for the notification to show.

We now had several failures where the first test actually wasn't able to navigate to the visualzie page. Even though it was put in a retry and waiting for the visualize page to be visible, and if not try to navigate to that page again, we ended up in several test cases, that it failed after the maximum retries, and the screenshot showed, that it was still on the Discover page (but the search was saved successfully there, as you can see in the page top menu bar).

I have no idea, what could cause the test framework not to execute that simple navigation properly, since it seems to work in a lot of cases, but the test failures for those on CI were actually rather often, so I think that the navigation has some severe flaws, we need to look into.

[stacey-gammon]

I don't see any more test failures in the last 60 days for "visualization from a saved search", so maybe this is obsolete now?