Pass testEnvironmentOptions as part of globalConfig to globalSetup and globalTeardown.

🚀 Feature Proposal

I would like to be able to reference testEnvironmentOptions inside of scripts passed in to globalSetup (and teardown).

Motivation

I am writing a custom environment.

I have some global setup that I would like to do like:

• Start chromedriver service that I want to run for ALL test suites.
• Clear out the log directory from previous runs.

I want the parameters like

• Which port to run the driver on
• What the log directory is to be defined in the jest.config.js. They are already defined there for me as part of my testEnvironmentOptions for my webdriver test environment. But the scripts in globalSetup and globalTeardown don’t have access to it.

Example

See motivation.

Pitch

This is the simplest change I can think of to accomplish what I need. I want to publish my jest-webdriver-environment, but right now I get around the limitation stated above by making fake projects that contain the flags I want to pass, since projects properties are considered part of the globalConfig.

Thank you for considering this.

[SimenB]

I still don’t fully understand, but it seems separate from what this PR asks for (which is already implemented). Could you open up a new feature request?

---

That said, we should have called globalSetup with an array of project configs, not just one. Might need to fix that in Jest 29.

---

Closing since projectConfig is available today

[github-actions[bot]]

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.