New issue
Advanced search Search tips

Issue 881828 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 1
Type: Bug-Regression

Blocking:
issue 807428



Sign in to add a comment

PrerenderTestCase fails with WKBasedNavigationManager

Project Member Reported by danyao@chromium.org, Sep 7

Issue description

Failing test with --enable-features=SlimNavigationManager flag:

testTapPrerenderSuggestions

Stacktrace:

../../ios/chrome/browser/prerender/prerender_egtest.mm:107: error: -[PrerenderTestCase testTapPrerenderSuggestions] : Exception: NoMatchingElementException
Exception Name: NoMatchingElementException
Exception Reason: Cannot find UI Element.
Exception with Assertion: {
  "Assertion Criteria":  "assertWithMatcher:matcherForSufficientlyVisible(>=0.750000)",
  "Element Matcher":  "(((respondsToSelector(isAccessibilityElement) && isAccessibilityElement) && accessibilityLabel('127.0.0.1:49467/test-page.html')) && ((kindOfClass('UIView') || respondsToSelector(accessibilityContainer)) && ancestorThatMatches(kindOfClass('OmniboxTextFieldIOS'))))",
  "Recovery Suggestion":  "Check if the element exists in the UI hierarchy printed below. If it exists, adjust the matcher so that it accurately matches element."
}
Exception Details: Error Trace: [
  {
    "Description":  "Interaction cannot continue because the desired element was not found.",
    "Error Domain":  "com.google.earlgrey.ElementInteractionErrorDomain",
    "Error Code":  "0",
    "File Name":  "GREYElementInteraction.m",
    "Function Name":  "-[GREYElementInteraction matchedElementsWithTimeout:error:]",
    "Line":  "124",
    "TestCase Class":  "PrerenderTestCase",
    "TestCase Method":  "testTapPrerenderSuggestions"
  }

 
Status: WontFix (was: Assigned)
This test is either flakey or fixed. I was not able to reproduce this failure locally or at a newer checkout 45fe7ce8c8152e60eda0b50afa25d8fb71945e92.

Sign in to add a comment