Those jest tests which are importing and mocking modules have deeply nested paths, while elsewhere in the app we are using aliased paths for the majority of module imports in our application.
Look into if it would be possible to also alias jest mocks and if so, update the paths.
Those jest tests which are importing and mocking modules have deeply nested paths, while elsewhere in the app we are using aliased paths for the majority of module imports in our application.
Look into if it would be possible to also alias jest mocks and if so, update the paths.
Example of a deeply nested path: https://github.com/cloud-gov/cg-ui/blob/main/__tests__/components/UsersActions/UsersActionsSpaceRoles/UsersActionsSpaceRoles.test.js#L13
Acceptance Criteria