Proposal: pass config to `globalSetup` and `globalTeardown`

[gregberge]

I am the maintainer of Jest Puppeteer project and I would like to suggest a new feature.

When I started Jest Puppeteer I wanted to make it as simple as possible. For this purpose, I wanted to be able to configure it only using Jest config. I found testEnvironmentOptions, it looked like the exact use case for me.

Jest Puppeteer needs globalSetup and globalTeardown, but these two methods do not have access to Jest config and by the way to testEnvironmentOptions. This is the reason why I introduced jest-puppeteer.config.js.

Today people are complaining about that additional config.

This was the context, now the request:

Could you pass config to globalSetup and globalTeardown? I think it is as simple as modifying this line.

Thanks for this amazing library!

[SimenB]

Works for me, PR welcome :)

[gregberge]

🎉

[backflip]

@neoziro, it looks like globalConfig does not include testEnvironmentOptions: https://github.com/facebook/jest/blob/master/packages/jest-config/src/index.js#L100-L152

Have you found a workaround for this?

I'm currently (mis)using projects: [{ myCustomConfig }].

[gregberge]

@backflip I didn't work on it for now. But yes it will be a problem for Jest Puppeteer.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.