Issue with Rendering <Outlet /> in Playwright Component Tests about playwright

[sand4rt]

Hey @bonchuk, could you make it easier to help by sending a minimal sample GitHub repository?

[bonchuk]

Description:
I am experiencing an issue with rendering the component from react-router-dom in my Playwright component tests. Specifically, I have a BoxLayout component that includes an , which should render the BoxScreen component when the URL matches /:language/basket/. However, the BoxScreen component is never shown during testing.

Expected Behavior:
The BoxScreen component should render correctly within the BoxLayout when the URL is /:language/box/.

Current Behavior:
The BoxScreen component does not render, and I am unable to verify its presence in the test.

Steps to Reproduce:

1. Set up a React component test with Playwright.
2. Include a BoxLayout component with an to render BoxScreen.
3. Use BrowserRouter and await page.evaluate(() => {
   window.history.pushState({}, '', '/com/box/');
   }); before mount to simulate the URL /:language/box/.
4. Observe that the BoxScreen component does not render.

test snippet:
test.only('box-empty @theme', async ({ mount }, testInfo) => { await page.evaluate(() => { window.history.pushState({}, '', '/com/box/'); }); const component = await mount( <WrapperForTests> <boxContext.Provider value={context}> <boxLayout /> </boxContext.Provider> </WrapperForTests>, ); const screenshot = await component.screenshot(); expect(screenshot).toMatchSnapshot(); }); });

Additional Information:

Library Versions:
react-router-dom: [6.11.2]
@playwright/experimental-ct-react: [1.39.0]
@playwright/test: [1.39.0],

Environment:
Node.js version: [v21.7.3]
npm version: [10.8.1]
Operating System: [ubuntu 22.04]

Request:
Could you please provide guidance on how to correctly render components nested within using playwright and react-router-dom in component tests? Any help or examples would be greatly appreciated.

[yury-s]

We need to be able to reproduce the problem to make this report actionable. Please file a new bug and provide a minimal reproducible example which we could run locally.