globalSetup not executed on watch reload

Do you want to request a feature or report a bug? Feature

What is the current behavior? When defining the globalSetup config option along with --watch, the globalSetup script only executes the first time the tests are run, not after each reload.

What is the expected behavior? It would be helpful to have some means of specifying a globalSetup script which would continue to be executed before all tests run after each reload triggered by --watch. Not sure if this ends up being a separate config option or what’s the best way of implementing it.

In terms of ‘why’, I’m using globalSetup to reset a test database for some integration tests. It would help if this option allowed this reset to continue to occur as --watch re-runs these tests.

[Surreal9]

Well; it seems to be working as expected in my new minimal jest + TS setup, must be something else in my config. Sorry for the false alarm, I’ll report back if I figure anything else out.

[mattphillips]

Hey @Surreal9 I can’t seem to replicate this behaviour.

I am able to run a globalSetup script in watch mode which logs the current date every time the tests are re-ran by hitting a or ENTER or from file changes.

Example globalSetup script:

module.exports = () => console.log(new Date());

Would you be able to create a repro to demo the issue?