Nice 👌 may I ask, do we really need the JEST_JASMINE env variable? Always found it a little odd that there is this one environment variable when we use the environment for almost nothing. It seems JEST_JASMINE=1 jest vs jest --testRunner=jest-jasmine isn't much of a difference, or am I missing something?

It's to ensure all of our tests are executed with the same runner, including e2e tests. It's not a public API sort of thing. Passing testRunner all over is painful I'd think. Maybe not?

(background: #6285)

I was thinking for those we have a centralized place in utils with runJest, but re-considering it there are probably lots of exceptions as well, plus most importantly I guess it's unsafe otherwise since you probably wouldn't notice if something doesn't use the intended runner.

huh, weird it failed on windows... will look into it later this week

This pull request 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.