@GiveMe-A-Name I believe this issue may need to be reopened, as #9057 only partially addresses the problem. I've included some examples in the original issue for your reference.

@haocheng6

in your reproduce steps, eg source-map-dev-tool-plugin-file-context/index.js case, the passed two case mean that the project under the test is compiled successfully; that's ok as expected.

and the failed case is failed due to expect(1).toBe(2) is also as expected.

@stormslowly Thank you for checking. The test case in source-map-dev-tool-plugin-file-context/index.js works as expected because it has been fixed by this recent PR #9057. The original issue lists a few other examples that need a proper fix because simply adding the findBundle option for those tests is not sufficient:

Examples of tests that are not executed and cannot be trivially fixed by simply adding a test.config.js file:

1. configCases/css/rspack-issue-4844
2. configCases/output-module/rspack-issue-6572
3. configCases/plugins/eval-source-map-dev-tool-plugin
4. configCases/split-chunks/used-exports
5. configCases/container-1-5/chunk-matcher (This one seems flaky. It passes or fails randomly.)

Here are the steps to reproduce the issue for the first example (configCases/css/rspack-issue-4844) above:

1. cd packages/rspack-test-tools/
2. Run pnpm run test:base -t config/css/rspack-issue-4844 -u and notice that two tests pass.
3. Create a new file packages/rspack-test-tools/tests/configCases/css/rspack-issue-4844/test.config.js with the following content:

/** @type {import("../../../..").TConfigCaseConfig} */
module.exports = {
    findBundle: (i, options) => {
        return ["main.js"];
    }
};

4. Run pnpm run test:base -t config/css/rspack-issue-4844 -u again and notice that this time two tests pass but one fails due to TypeError: Cannot read properties of null (reading 'length').