Stubbed async components for Jest
What does this MR do?
Stubs the async components for Jest tests to prevent the tests from timing out. The issue happens due to the need of fetching the async components at the run-time.
Screenshots (strongly suggested)
It's the developer-facing change, hence no changelog entries.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Relates to #280809 (closed)
Edited by Denys Mishunov