Address review: fix renderAppComponent option name, add configureFusion test

- docs/advanced.md: the 'choose a rendering API' table row for
  renderAppComponent still said configureApp, but that imperative
  helper's own option was never renamed -- it's still configure.
- testApp.test.tsx: add coverage for the configureFusion fixture,
  asserting a memory history pushed onto ahead of framework
  initialization is observable from a rendered component, proving
  configureFusion ran before the framework finished resolving.

Author: odinr

packages/react/app/src/__tests__/testApp.test.tsx

@@ -3,6 +3,9 @@ import { describe, expect } from 'vitest';
 import { enableContextMock } from '@equinor/fusion-framework-module-context/mock';
 import type { ContextItem } from '@equinor/fusion-framework-module-context';
 import { useCurrentContext } from '@equinor/fusion-framework-react-app/context';
+import { useFramework } from '@equinor/fusion-framework-react';
+import { createHistory, enableNavigation } from '@equinor/fusion-framework-module-navigation';
+import type { NavigationModule } from '@equinor/fusion-framework-module-navigation';
 
 import { testApp } from '@equinor/fusion-framework-vitest-plugin-react-app/test';
 
@@ -44,4 +47,30 @@ describe('testApp', () => {
       await expect.element(screen.getByText(projectA.title as string)).toBeVisible();
     });
   });
+
+  describe('with a configured parent framework', () => {
+    const NavigationLocation = () => {
+      const { navigation } = useFramework<[NavigationModule]>().modules;
+      return <p>{navigation.history.location.pathname}</p>;
+    };
+
+    // pushed on the history instance itself, before it's handed to the framework configurator,
+    // so a passing assertion also proves `configureFusion` ran ahead of framework initialization
+    const history = createHistory('memory');
+    history.push('/configured-by-configure-fusion');
+
+    const test = testApp.extend(
+      'configureFusion',
+      { injected: true },
+      () => (configurator) =>
+        enableNavigation(configurator, { configure: (config) => config.setHistory(history) }),
+    );
+
+    test('resolves the fusion instance with the configured navigation history', async ({
+      render,
+    }) => {
+      const screen = await render(<NavigationLocation />);
+      await expect.element(screen.getByText('/configured-by-configure-fusion')).toBeVisible();
+    });
+  });
 });

packages/vitest-plugin/react-app/docs/advanced.md

@@ -15,7 +15,7 @@ and the general `test.extend`/`test.override` mechanics Fusion builds on.
 | `test` from `/test` | The app's manifest, config, and module configurator should resolve automatically |
 | `render` from `/test` | A standard `describe` or `it` block needs the automatically resolved app scope |
 | `renderAppHook` | A hook needs an app scope with explicitly supplied options |
-| `renderAppComponent` | A component needs explicit `env`, `configureApp`, or parent `fusion` options |
+| `renderAppComponent` | A component needs explicit `env`, `configure`, or parent `fusion` options |
 | `testApp` | A reusable fixture should not depend on Vite's automatic app-file resolution |
 
 All Fusion rendering APIs initialize modules asynchronously and must be awaited. The lower