Async/Await in custom testEnvironment

[KhaledSakr]

According to the docs, a custom test environment can be setup this way:

const NodeEnvironment = require('jest-environment-node');

class CustomEnvironment extends NodeEnvironment {
  constructor(config) {
    super(config);
  }

  async setup() {
    await super.setup();
    await someSetupTasks();
    this.global.someGlobalObject = createGlobalObject();
  }

  async teardown() {
    this.global.someGlobalObject = destroyGlobalObject();
    await someTeardownTasks();
    await super.teardown();
  }

  runScript(script) {
    return super.runScript(script);
  }
}

But when I do that, I get the following errors

 FAIL  tests\user.test.js
  ● Test suite failed to run

    D:\everest\tests\env.js:8
      async setup() {
            ^^^^^

    SyntaxError: Unexpected identifier

      at node_modules/jest-runner/build/run_test.js:31:29

Code:
env.js

[SimenB]

Your runtime has to support async-await (so use node 8 or newer) or you need to transpile.

PR welcome with a doc update highlighting that fact!

[KhaledSakr]

But doesn't jest already transpile the code? We can use async/await out of the box in test files.

[SimenB]

It transpiles your tests, not config files.

You can track #5164 for it (feel free to add a comment about jest-environment as well there 🙂)

[KhaledSakr]

I see, thank you!

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