yarn test:integration Taking Around 2 Hours — Is This Expected?

[bodhekarvarad]

Hi everyone,

I'm setting up the Webpack repository and ran:

yarn test:integration

The integration test suite has been running for around 2 hours.

Is this expected for the full Webpack integration test suite, or could there be an issue with my local setup?

My environment:

• OS: Windows + WSL2
• Node.js: v24.8.0
• Yarn: v1.22.22

Should I let the test suite finish, or is there a recommended way to run only the relevant integration tests for a specific contribution?

Thanks!

[xiaoxiaojx]

hi @bodhekarvarad, Running the full yarn test:integration suite can take a long time because it covers a large number of configuration cases. For a specific contribution, it is usually better to run the relevant test case directly, for example:

yarn test:base --testPathPatterns=test/ConfigTestCases.basictest.js --testNamePattern="lazy-barrel"

The exact duration also depends on the filesystem performance of the WSL2 environment.

[bodhekarvarad]

Thanks @xiaoxiaojx for the clarification!!!I understand that yarn test:integration runs the full integration test suite and can take a long time.

I want to make sure my local Webpack repository is fully set up and working before I start contributing. Is there a recommended way to verify the complete local setup without running the full integration test suite, since it takes a lot of time in my WSL2 environment?

because it takes a lots of time for setup a project locally about 2 horus thats why is any another via or command for setup.
This problem I am faced for setup