coverageDirectory should be specified by default

[TrySound]

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

I have

• package.json with "test": "jest --coverage" script
• test/test.js
  and when I run test script I got coverage placed in test/coverage while I expect <rootDir>/coverage
  In different projects I got coverage in root dir and I don't know what is the reason for it.

What is the expected behavior?

More clean coverageDirectory default

Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.

[email protected]
yarn 0.24.5
windows@8

[thymikee]

Can you provide a repro?

[TrySound]

I guess it's because some of my projects used process.chdir('test'). Forgot about it
Is it expected behavior then?

[thymikee]

No, I don't think so. @aaronabramov should we add this to install_common_globals?

[aaronabramov]

i'm not sure why this can happen. coverageDirectory is always set from <rootDir> + coverage. The only way it can happen if rootDir is not specified explicitly and process.chdir is called before the config is read. this way rootDir will default to cwd

[TrySound]

Why docs say it undefined?

[aaronabramov]

actually.. right.
it checks for coverageDirectory here, and since it's undefined, istanbul uses its own default, which is process.cwd() + '/coverage'.

@thymikee i think we should have a default value for this option, since practically it can't be undefined

[TrySound]

Nice. Thanks.

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