Bug 1810726

Summary:	Jest configuration is excluding OLM unit tests
Product:	OpenShift Container Platform	Reporter:	Jon Jackson <jonjacks>
Component:	Management Console	Assignee:	Jon Jackson <jonjacks>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, jokerman, yapei
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Test files were moved, and configuration was not updated Consequence: OLM Unit tests were not running Fix: Update configuration to include new location of OLM unit test files. Result: OLM unit tests run, but many fail because of changes that occurred in the interim. Updated as many as possible, but some are disabled for now.	Story Points:	---
Clone Of:
Clones:	1810745 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:18:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1810745

Description Jon Jackson 2020-03-05 19:26:02 UTC

Description of problem:
Jest configuration excludes OLM Unit tests

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

How reproducible:
Always

Steps to Reproduce:
run 'yarn test' in the console repo

Actual results:
OLM unit tests are not run

Expected results:
OLM unit tests should run and pass

Additional info:
I adjusted the config to run the unit tests, and most of them were failing. I've begun fixing them and have the failure count down to about 17 at this point.

Comment 3 Yadan Pei 2020-03-09 08:49:28 UTC

clone openshift/console and change to frontend dir, run `yarn test` , we can see unit tests in packages/operator-lifecycle-manager/ directory are executed.


Moving to VERIFIED

Comment 5 errata-xmlrpc 2020-07-13 17:18:35 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, 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:2409