Apply appropriate configs for different tests ran as different projects

[deser]

Hi Guys.
Seems projects doesn't work as intended. I have jest config which is intended to run all my type of tests:

module.exports = {
    projects: ['./jest.config.ui.js', './jest.config.unit.js']
};

It is impossible that file of unit tests would be grabbed by ui tests, see regex:
ui: testRegex: '/__tests__/.*-test\\.js?$',
unit: testMatch: ['**/__tests__/**/?(*.)+(spec).js']

These ui and unit configs have different setups. For example for ui tests I need to resolve all css files successfully, I do this via:

 moduleNameMapper: {
        '\\.(jpg|jpeg|png|gif|eot|otf|webp|svg|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga)$':
            './resources/__mocks__/fileMock.js',
        '\\.(css|sass|scss|less)$': 'identity-obj-proxy'
    },

unit tests config doesn't have this setup.

So, when I run ui and unit tests separately - all good.
When I try to run all tests config - I see that moduleNameMapper doesn't work for ui tests.

In total, expected behaviour:
File which is found for UI test should be executed with the help of appropriate config.

UPD: DEMO
To see behavior please clone repo https://github.com/deser/jest_issue-7268 and follow steps in README.md

[deser]

UPD: I suspect that my issue is connected with #7186
Could you confirm? When is new release with that fix is planned?

[deser]

UPD: When I run the same failing test filtering it via --testNamePattern= it works correctly

[deser]

Guys, any thoughts?

[SimenB]

@deser you can try installing jest 24 prerelease (yarn add --dev jest@beta) which includes #7186 to verify.

If it does not help, you need to update the OP with the information from the issue template, most importantly including a full reproduction case

[deser]

Sure, I'll feedback

[deser]

Nope, it didn't help. I'll update description.

BTW, project didn't run successfully. It complained about babel 6. I had to remove jest and babel-jest and install again

[deser]

@SimenB , please see demo

[deser]

UPD: Seems this issue is resources dependent. On my machine tests fail, when on another they doesn't.
If tests doesn't fail on your machine I assume you can throttle your CPU to reproduce the issue.

My machine:
System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
Binaries:
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD

Node: 10.11.0

Also, as you can notice I've created a lot tests inside, because when I had just a few of them - issue weren't reproduced. This indirectly approves my thought that the issue is resources dependent.

[deser]

Guys, any updates\thoughts on the issue?

[rickhanlonii]

Hey @deser, sorry for the delay - reading through this it's hard to understand what the issue is

Can you dumb this down for me?

[deser]

Yes, sure. In 2 words projects feature works incorrect. It is expected that it will run a test through appropriate config for appropriate match within the config. But under certain circumstances it behaves incorrect, running a test with incorrect config.

[wilkinsonjack1993]

Also experiencing similar issues, projects basically does not work.

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days.