global beforeAll

[shai32]

is there any way for a global beforeAll?

I can define beforeAll in each test file but this will run the beforeAll once for each test file.

is there any global beforeAll that will be run once and finishes before the first test start?

[ashtonsix]

Have you seen setupFiles?

For reference my project uses setupFiles like this:

package.json

{
  "jest": {
    "setupFiles": [
      "./private/mocks/runtime.js"
    ]
  }
}

./private/mocks/runtime.js

global.__meteor_runtime_config__ = {ROOT_URL: 'localhost'};

FYI Stack Overflow might be a better place for this kind of question. (question about usage instead of a bug report / feature request).

Also I've unsubscribed from this issue so won't get any notifications if you reply.

[shai32]

I am using create-react-app.
and setupFiles run again for each test file.

giving an answer that isn't correct and closing an issue after it. bravo!

[nalejandroveron]

@cpojer @ashtonsix I don't think that this should be closed and the answer is not correct, both setupFiles or setupTestFrameworkScriptFile runs for each test suite, so there is not a "global" beforeAll where we can set thinks like cleaning a test db before testing on

[SimenB]

You can have a pretest in package.json?

[ashtonsix]

@Negan1911 - maybe, but it's difficult to tell what's meant in the OP. You could consider creating a second issue if you think it's a useful feature & want to bring more clarity to this feature request?

[v1adko]

@cpojer @ashtonsix If I understand it correctly, currently it's not possible to have global setup and teardown like discussed here in Mocha.
The use-case that I (and probably the OP) have is that I want to run a server and only then all of my integration tests (and probably after all of them have run drop the test DB).
Do you have any advice or best-practices for doing this?
What I've found is people mostly telling to startup a server and close it for each test suite in "local" beforeAll/afterAll, e.g. here by @kentcdodds, but implies a lot of duplication, no?

[joaomilho]

+1 on having a global setup, in my use case I wanna run a proxy server as well

[danpalmer]

@ashtonsix for what it’s worth, the OP was clear in my opinion. I’d like this issue to be re-opened.

[cpojer]

You can create a custom jest-environment, see jest-environment-node or jest-environment-jsdom and subclass it. It should allow you to set up the environment in any way you like. We discussed adding an async hook for this also, and I'm happy to accept PRs for it.

[wubzz]

+1 Wanted to try jest coming from mocha and was impressed with the ease of jest-codemods and the docs, up until I got stuck with this same issue.

Every first describe of each seperate file was taking surprisingly long to execute. Turns out the setup was - as explained by previous comments - run once per file, resulting in tons of unecessary time consuming operations such as DROP DATABASE, CREATE DATABASE, and more.

Unfortunately there's no workaround in the docs (which in turn brought me here) except to run node setup.js && jest which is not ideal..

[tuomash]

+1 for global setup. Like other users, I'd like to setup and tear down the app/DB only once.