Bug 1871699 - Fixed ocs installation e2e tests to incorporate the new changes on OLM pages
Summary: Fixed ocs installation e2e tests to incorporate the new changes on OLM pages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.7.0
Assignee: Bipul Adhikari
QA Contact: Elena Bondarenko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-24 04:53 UTC by Neha Gupta
Modified: 2020-12-11 11:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-11 11:20:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 6336 0 None closed Bug 1871699: Fixed ocs installation tests to incorporate the new changes on OLM pages 2020-12-11 11:15:58 UTC

Description Neha Gupta 2020-08-24 04:53:27 UTC
Description of problem:
Fixed ocs installation e2e tests to incorporate the new changes of OCP 4.6 on OLM pages

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Elena Bondarenko 2020-09-22 14:32:13 UTC
I tried OCS installation from the master branch today. It got stuck on the Operator Hub page: the filter for OpenShift Container Storage was applied correctly, but the click didn't happen so OCS was not installed.

Comment 4 Nishanth Thomas 2020-09-22 17:47:33 UTC
Moving this out of 4.6

Comment 6 Bipul Adhikari 2020-12-11 11:20:05 UTC
We are moving to Cypress. 
In the first stage, we are migrating "Installation Tests", "Add Capacity" and "Dashboard Tests".

Closing this BZ because we are choosing to focus our efforts on migrating our tests to Cypress than to fix tests present in Protractor.


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