Flaky Frontend tests failing every time while pushing changes

This error occurred recently locally on my machine when running the frontend tests

Chrome Headless 87.0.4280.88 (Mac OS 11.0.0) Upgraded component should create the upgraded component FAILED
	Failed: Uncaught (in promise): TypeError: Class constructor UpgradeComponent cannot be invoked without 'new'
	TypeError: Class constructor UpgradeComponent cannot be invoked without 'new'
	    at new CollectionPermissionsCard (core/templates/combined-tests.spec.js:44348:19139)
	    at createClass (core/templates/combined-tests.spec.js:193077:20)
	    at createDirectiveInstance (core/templates/combined-tests.spec.js:192954:22)
	    at createViewNodes (core/templates/combined-tests.spec.js:200043:38)
	    at callViewAction (core/templates/combined-tests.spec.js:200359:13)
	    at execComponentViewsAction (core/templates/combined-tests.spec.js:200278:13)
	    at createViewNodes (core/templates/combined-tests.spec.js:200071:5)
	    at createRootView (core/templates/combined-tests.spec.js:199952:5)
	    at callWithDebugContext (core/templates/combined-tests.spec.js:200926:27)
	    at Object.debugCreateRootView [as createRootView] (core/templates/combined-tests.spec.js:200471:12)
	error properties: Object({ rejection: TypeError: Class constructor UpgradeComponent cannot be invoked without 'new', promise: [object Promise], zone: Zone({ _parent: Zone({ _parent: null, _name: '<root>', _properties: Object({  }), _zoneDelegate: ZoneDelegate({ _taskCounts: Object({ microTask: 0, macroTask: 0, eventTask: 0 }), zone: <circular reference: Object>, _parentDelegate: null, _forkZS: null, _forkDlgt: null, _forkCurrZone: null, _interceptZS: null, _interceptDlgt: null, _interceptCurrZone: null, _invokeZS: null, _invokeDlgt: null, _invokeCurrZone: null, _handleErrorZS: null, _handleErrorDlgt: null, _handleErrorCurrZone: null, _scheduleTaskZS: null, _scheduleTaskDlgt: null, _scheduleTaskCurrZone: null, _invokeTaskZS: null, _invokeTaskDlgt: null, _invokeTaskCurrZone: null, _cancelTaskZS: null, _cancelTaskDlgt: null, _cancelTaskCurrZone: null, _hasTaskZS: null, _hasTaskDlgt: null, _hasTaskDlgtOwner: null, _hasTaskCurrZone: null }) }), _name: 'ProxyZone', _properties: Object({ ProxyZoneSpec: Pro ...

Additional context When trying to push the changes to an existing PR, the frontend tests are failing every time to give the error as mentioned above. Even after trying to push the code again and rerunning the tests too, the frontend tests are failing which are most probably flakes as the frontend tests passed after the changes were pushed.

[atpug22]

@parulpriyedarshani Yes, yesterday this happened to me also. While running the frontend tests all checks were passed but just after this when I tried pushing my code I got the same error in frontend tests. But when I tried after some time without making any changes in the code it showed no error and the code was pushed.

[U8NWXD]

Frontend flakes have been fixed