STCOR-913 Don't override initial discovery and okapi data in test moc…

…ks (#1564)

Updating `stripes-core` in SSC causes 30+ tests to fail.
folio-org/stripes-smart-components#1538
This PR addresses some issues which cause these failures.

Overwriting of initial okapi and discovery data in `setupApplication`
helper. Some tests require custom okapi data, but `setupApplication` in
some cases can overwrite that data which makes those tests fail.

Still investigating a few failing tests so maybe there's something
else that needs to be fixed.

CHANGELOG.md

@@ -7,7 +7,7 @@
 * Send the stored central tenant name in the header on logout. Refs STCOR-900.
 * Provide `<IfAnyPermission>` and `stripes.hasAnyPermission()`. Refs STCOR-910.
 * Use the `users-keycloak/_self` endpoint conditionally when the `users-keycloak` interface is present; otherwise, use `bl-users/_self` within `useUserTenantPermissions`. Refs STCOR-905.
-
+* Don't override initial discovery and okapi data in test mocks. Refs STCOR-913.
 
 ## [10.2.0](https://github.com/folio-org/stripes-core/tree/v10.2.0) (2024-10-11)
 [Full Changelog](https://github.com/folio-org/stripes-core/compare/v10.1.1...v10.2.0)

test/bigtest/helpers/setup-application.js

@@ -42,6 +42,7 @@ export default function setupApplication({
     // when auth is disabled, add a fake user to the store
     if (disableAuth) {
       initialState.okapi = {
+        ...initialState.okapi,
         currentUser: assign({
           id: 'test',
           username: 'testuser',
@@ -55,10 +56,12 @@ export default function setupApplication({
         isAuthenticated: true,
       };
       initialState.discovery = {
+        ...initialState.discovery,
         isFinished: true,
       };
     } else {
       initialState.okapi = {
+        ...initialState.okapi,
         ssoEnabled: true,
       };
     }