Add current test file path in process.env

🚀 Feature Proposal

Absolute path to currently running test file in process.env

Motivation

When there are different “groups” of test files (e.g., usage in different environments or module systems), sometimes the difference between the groups is too minor to have an entirely separate Jest configuration file, separate run command etc. In this case, when having a simple if..else clause in setup files would be ideal, there is nothing to distinguish one setup from another.

Example

{
  "setupFiles": [
    "<rootDir>/test/setup.js"
  ]
}

// test/setup.js
console.log(process.env.JEST_TEST_FILE_PATH); // identifier is up to dispute

$ jest

● Console

  console.log test/setup.js:1
    /path/to/project/test/my-entity.spec.ts

Pitch

Not sure what’s that

[SimenB]

Ah right, missed that part of your use case.

Yeah, we ship a browser like (backed by JSDOM) and a node like environment, so if that’s all you need you should be good. in a setup file you can do something like if (typeof window !== 'undefined') {.

Thanks for the PR regardless, even if it wasn’t merged! 👍

[parzhitsky]

@SimenB, @jeysal I’m impressed, how friendly and helpful you guys are! Thank you very much 👏