CODEWITHSUNDEEP
javascriptjestjs
Roy
Roy

Reputation: 2808

Jest run async function ONCE before all tests

I want to use jest for my server unit testing (instead of mocha+chai). Is there a way I can run async function before all tests start (init purposes) only once and not for every test file? And also if there's a way of running something after all tests are done?

Upvotes: 90

Views: 81661

Answers (6)

CyberT33N
CyberT33N

Reputation: 144

For next.js it work like this:

  • vitest.config.ts
import { defineConfig } from 'vitest/config'
import react from '@vitejs/plugin-react'
import tsconfigPaths from 'vite-tsconfig-paths'
 
export default defineConfig({
    plugins: [tsconfigPaths(), react()],
    test: {
        environment: 'jsdom',
        // setupFiles: ['/tests/setup-tests.ts'],
        globalSetup: 'test/setup-tests.ts'
    }
})
  • test/setup-tests.ts
// ==== NEXT.JS ====
import { loadEnvConfig } from '@next/env'
loadEnvConfig(process.cwd())

// ==== BOOTSTRAP ====
import { bootstrap } from '@/src/bootstrap'
export default bootstrap

Upvotes: 0

Raj Gohil
Raj Gohil

Reputation: 217

It's become very easy when you use beforeAll function outside the describe block and then assign async keyword to it.

Note: I am using jest @27.4.3 version here

code sample

import { getValuesFromAWSSecretManager } from '../../src/libs/secret_manager';
import quickbooksConfigFrom from '../../src/config/quickbooks';

const quickbooksConfig = quickbooksConfigFrom;

// calling the async beforeALL function to get values from AWS Secret Manager
beforeAll(async () => {
  const secretData = await getValuesFromAWSSecretManager();
  quickbooksConfig.clientId = secretData.QUICKBOOKS_CLIENT_ID;
  quickbooksConfig.clientSecret = secretData.QUICKBOOKS_CLIENT_SECRET;
});

describe('Quickbooks config file should be defined', () => {
  test('Quickbooks File should be exist', () => {
    expect(quickbooksConfig).toBeDefined();
  });

  test('Quickbooks File should be exist and having values', () => {
    expect(quickbooksConfig).toBeTruthy();
  });
});

hope it helps and solves your doubts,

and you might need to do it in each file to apply.

you can check jest beforeAll documentation from here

Upvotes: 1

Amaury Liet
Amaury Liet

Reputation: 11193

This feature was added in Jest's 22 version, with globalSetup and globalTeardown configurations. Look at this for examples.

package.json (or in jest.config.js)

{
  ...
  "jest": {
    "globalSetup": "./scripts/jestGlobalSetup.js"
  }
}

/scripts/jestGlobalSetup.js

module.exports = async () => {
  console.log('\nhello, this is just before tests start running');
};

OR

export default async () => {
  console.log('\nhello, this is just before tests start running');
};

Upvotes: 88

Raheel Riaz
Raheel Riaz

Reputation: 251

jest provides options for both global setup and teardown in new versions. You can create files for both setup and teardown exporting an async function and provide that path in jest configurarion like this.

"globalSetup": "setup-file-path",
"globalTeardown": "tear-down-file-path"

You can read about it further here

Upvotes: 9

Michael Jungo
Michael Jungo

Reputation: 33010

Jest provides beforeAll and afterAll. As with test/it it will wait for a promise to resolve, if the function returns a promise.

beforeAll(() => {
  return new Promise(resolve => {
    // Asynchronous task
    // ...
    resolve();
  });
});

It also supports callback style, if you have some existing test code that uses callbacks, although it's recommended to use promises.

beforeAll(done => {
  // Asynchronous task
  // ...
  done();
});

Upvotes: 21

Lauri Lüüs
Lauri Lüüs

Reputation: 199

If you execute jest tests with npm you can run any node command or any executable before executing other command

"scripts": {
    "test": "node setup.js && jest"
  }

so now you can run this with command

$ npm t

Upvotes: 5

Related Questions