Simen Bekkhus

We do set it to `null` manually in the node environment, FWIW. https://github.com/jestjs/jest/blob/00ef0ed0a03764f24ff568bc87dcc1c203d28625/packages/jest-environment-node/src/index.ts#L200 Not so in the JSDOM env, but the reproduction in this issue uses the Node env. Might...

I think ditching the coverage if tests fail makes sense. @thymikee @jeysal thoughts? We can probably get that into Jest 25

There is no performance issue in "Collecting coverage from untested files" (or, there _is_, but that's totally orthogonal to the issue reported here) - the issue here is that `bail`...

PR welcome 🙂

Can you set up a reproduction without `ts-jest`? That's not maintained in this repo

Thanks for the detailed proposal! This is related to #4257 - whatever API we come up with should work with both Flow and TS. I don't know enough (about either...

`jest-mock` has seen extensive improvements to its types in Jest v28 via #12435, #12442 and #12489 ```ts import {jest} from '@jest/globals'; interface MyApi { someMethod(x: number): string; someOtherMethod(): void; someThirdMethod():...

You can also do [`jest.createMockFromModule('some-module')`](https://jestjs.io/docs/jest-object#jestcreatemockfrommodulemodulename) (this is what `jest.mock` does under the hood if you don't provide a mock factory). But if you don't want to mock at the module...

If you by "plain properties" mean primitives, then yes. And classes or arrays. We also detect generator functions or async functions and return the correct type of function. Both sinon...

Good point! Wanna send a PR with this addition?