Bug 1890235 - e2e: update Protractor's checkErrors logging
Summary: e2e: update Protractor's checkErrors logging
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: David Taylor
QA Contact: Yadan Pei
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-21 17:57 UTC by David Taylor
Modified: 2021-02-24 15:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-02-24 15:27:22 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 7019 0 None closed Bug 1890235: update Protractor's checkErrors logging 2020-11-18 04:46:16 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:27:46 UTC

Description David Taylor 2020-10-21 17:57:01 UTC
Protractor traps and logs window errors, need to update logging to include reason/cause.

Currently logs:

Error: Failed: omg js error: [object Object]

Raised here: [https://github.com/openshift/console/pull/6932#issuecomment-712180465]

Cypress does this here: https://github.com/openshift/console/blob/5464e1058c275f95a29688fbe2f5c192de0f78b7/frontend/packages/integration-tests-cypress/support/index.ts#L42

Comment 4 Yadan Pei 2020-11-18 13:30:42 UTC
1. Check CI log error logs and Cypress error log is updated, for example https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_console/7137/pull-ci-openshift-console-master-e2e-gcp-console/1328926760540049408
2. Clone console repo and run Protractor tests, check failure log and it is updated with detail error message

Moving to VERIFIED

Comment 7 errata-xmlrpc 2021-02-24 15:27:22 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

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


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