Global configs in presets silently fail when set on a project.

[captbaritone]

🐛 Bug Report

I tried to install jest-puppeteer on Webamp and their docs advised me to add

{
  "preset": "jest-puppeteer"
}

to my "Jest Config".

Since I wanted these slow integration tests to be run separately from my normal tests, I created a new project for my integration tests. Unfortunately this did now work, since this preset contains some global configs:

{
  "globalSetup": "jest-environment-puppeteer/setup",
  "globalTeardown": "jest-environment-puppeteer/teardown",
  "testEnvironment": "jest-environment-puppeteer",
  "setupTestFrameworkScriptFile": "expect-puppeteer"
}

After adding the two global values to my root config, things seemed to work fine.

I'm not sure what the right solution is here:

1. Hoist global config? This is bad because it defies the user's expectation that projects are independent.
2. Error when you try to add a preset with a global value to a project?
3. Disallow presets on projects all together?

@SimenB

[SimenB]

The main issue I think is that it silently did not work - we're missing some validation of the shape of the configs after separating them.

As for correct behavior I think we'd have to either hoist magically global ones out of projects, or throw an explicit error saying it's not possible.

@cpojer?

[cpojer]

Oh.. preset was designed before the config split happened. I'm not sure right now what the right solution is, though.

[SimenB]

Duplicate of #5441