Access to jest runtime from setupTestFrameworkScriptFile

[simenbrekken]

I'd like to add some more mocking methods to jest but there doesn't seem to be an easy way to add methods to the jest object.

[lxanders]

This is a problem for me too.

There are scripts that are meant to run before the tests. These two are the ones that sound good for executing code :

• config.setupTestFrameworkScriptFile

The path to a module that runs some code to configure or set up the testing framework before each test. Since config.setupEnvScriptFile executes before the test framework is installed in the environment, this script file presents you the opportunity of running some code immediately after the test framework has been installed in the environment.

• config.setupEnvScriptFile

The path to a module that runs some code to configure or set up the testing environment before each test. Since every test runs in it's own environment, this script will be executed in the testing environment immediately before executing the test code itself.
It's worth noting that this code will execute before config.setupTestFrameworkScriptFile.

Reading this it sounds like the script specified by setupTestFrameworkScriptFile is the latest moment you can pre run code before the tests are started. I can confirm that there seems to be no way to access the jest object in these files.

One good reason for exposing the jest object: We had massive problems with the auto mocking and disabling it fixed the problems for us. As there is no configuration option for disabling this per run, you have to call jest.autoMockOff(); in each test. Moving this out in a pre run script would have been an acceptable workaround for the missing config / run switch for it.

[ncuillery]

👍

[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.