Add runInBand to the config object passed into the Test Environment constructor

[johncmunson]

🚀 Feature Proposal

Add runInBand to the config object passed into the Test Environment constructor. Is there a specific reason this property is excluded, while other properties such detectOpenHandles are not?

Motivation

Setup/Teardown can be subtly different depending on the mode that tests are being executed.

Example

async teardown() {
  // Tests will all use the same connection if running in sequence, but they
  // will each have their own connection if running in parallel. This is due
  // to the app using a shared singleton to connect to the database. If tests
  // are running in sequence, defer closing knex to the global teardown file.
  if (!this.config.runInBand) {
    await knex.destroy()
  }
  await super.teardown()
}

[WeiAnAn]

We can set JEST_RUN_IN_BAND environment variable to do the same thing!.
I create a PR.

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

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