Bug 1880117 - Protractor e2e test flake: display Global Configuration page, click Explore Console API in dropdown link
Summary: Protractor e2e test flake: display Global Configuration page, click Explore C...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.6.0
Assignee: David Taylor
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks: 1880118
TreeView+ depends on / blocked
 
Reported: 2020-09-17 17:40 UTC by David Taylor
Modified: 2020-10-27 16:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1880118 (view as bug list)
Environment:
Last Closed: 2020-10-27 16:42:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 6648 0 None open Bug 1880117: Fix Protractor flake: display Global Configuration page, click Explore Console API in dropdown link 2020-09-17 17:45:44 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:42:33 UTC

Description David Taylor 2020-09-17 17:40:03 UTC
This protractor test fails with: NoSuchElementError: No element found using locator: By(css selector, [data-test-id="api-explorer-resource-title"]), even though screenshot shows the correct html element and upon inspection, the element does have the correct data-test-id.

Proposed fix is to introduce a browswer.wait until html element is present.

Comment 6 errata-xmlrpc 2020-10-27 16:42:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4196


Note You need to log in before you can comment on or make changes to this bug.