Bug 1871220 - console e2e test that creates a namespace does not use a consistent name
Summary: console e2e test that creates a namespace does not use a consistent name
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
Depends On:
TreeView+ depends on / blocked
Reported: 2020-08-21 16:00 UTC by Samuel Padgett
Modified: 2020-10-27 16:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Version: 4.6.0-0.nightly-2020-08-02-134243 Cluster ID: f5e2e915-8a19-4378-bc89-b4fb9e0b911e Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:80.0) Gecko/20100101 Firefox/80.0
Last Closed: 2020-10-27 16:30:38 UTC
Target Upstream Version:

Attachments (Terms of Use)
Verification screenshot (141.37 KB, image/png)
2020-09-02 07:41 UTC, XiaochuanWang
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 6331 0 None closed Bug 1871220: use consistent test names in base scenario 2020-09-02 05:04:36 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:30:51 UTC

Description Samuel Padgett 2020-08-21 16:00:25 UTC
In our protractor tests, we have a test that creates the test namespace for the rest of the suite. This test includes the namespace name in its test name in the JUnit report. This confuses tools like testgrid and sippy. It looks like different tests each run because the name changes.

Comment 4 XiaochuanWang 2020-09-02 07:41:24 UTC
Created attachment 1713408 [details]
Verification screenshot

Comment 5 XiaochuanWang 2020-09-02 07:46:48 UTC
Test scenarios is using variable for namespace now. Attached the log screenshot for refer. Moving to Verified.

Comment 8 errata-xmlrpc 2020-10-27 16:30:38 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.


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