jest --init does not enable collectCoverage

[davc0n]

🐛 Bug Report

Not sure if a bug or if my thinking is just wrong.
During init, when prompted for coverage report, in case of positive answer the generated config has not collectCoverage set to true. Additionally, in case of negative answer it still asks for which provider to choose, which shouldn't really matter in that case and consequently not asked.

To Reproduce

• Run jest --init
• Do you want Jest to add coverage reports? … yes

Expected behavior

Config file should have collectCoverage: true.

envinfo

  System:
    OS: Linux 5.11 Arch Linux
    CPU: (8) x64 AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx
  Binaries:
    Node: 14.16.0 - /usr/bin/node
    npm: 7.10.0 - /usr/bin/npm
  npmPackages:
    jest: ^26.6.3 => 26.6.3 

[SimenB]

I think it makes sense to still ask about coverageProvider as you might want to use --coverage later even if you don't want it in config.

Not putting it in when responding positively sounds like a bug, though. Wanna send a PR fixing it?

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