Rspack is running webpack tests to discover current implementations and functionalities misaligned with webpack.

Our goal is to maintain consistency with webpack as much as possible, but there are still some features that require discussion to determine whether or not to support them. These include APIs that have alternative ECMAScript standards or features that have high support costs but are used by very few people. This issue is meant to track these inconsistencies, and we will continue to improve test coverage and pass rates in the future.

We have already run some tests at the moment. Of course, we welcome your help in advancing the testing progress and discovering any issues. This may require a certain level of familiarity with webpack's code to identify the underlying causes of test failures.

The following are the steps to advance the testing progress:

1. Run pnpm run build:cli:debug or pnpm run build:cli:release to make sure you are on the latest build.
2. cd webpack-test and find a test that you want to run.
3. Make sure the test.filter.js under the test case is returning true.
4. Run pnpm run test -- -t "test name", for example, if you want to run webpack-test/cases/amd/define-needs-module, you can use the following command pnpm run test -- -t "amd define-needs-module"
5. If it passes, then you can remove test.filter.js under the test case.
6. If it doesn't passes, then you need to find the reason why it failed, and make test.filter.js return a string that contain the reason, and it would be better to create a issue and use the link as the reason, for example module.exports = () => {return "https://github.com/web-infra-dev/rspack/issues/4313"}

And the principle is not to modify the code of webpack-test's test to make the test passes. Instead, focus on tracking all inconsistencies as much as possible.

Here are some of the identified issues: