[Internal] Jest runner limitations / adoption blockers

[pavelfeldman]

• No incremental progress
  Report progress of individual test cases jestjs/jest#6616
  open since Jul 4, 2018, positive signals, pending PRs
• No configurable thresholds - all e2e tests are red/slow
  Custom threshold for test time warning/errors jestjs/jest#7220
  open since Oct 19, 2018, no signals from maintainers
• No way to skip tests programmatically based on the environment
  Allow to skip tests programmatically jestjs/jest#7245
  closed as won't fix, no positive signals from maintainers
• Specify whether to run only focused tests or all tests
  • Most of the time, I'd like to run just one test, not one test in one file and all other files
  • At the same time, I don't want to skip test runs if I accidentally commit it.only
• Pass different values to a test function, depending on command line options
• Dynamically add command line options
• Control focusing and skipping of tests based on the command line option
• Jest runs workers proactively, will run 40 workers even if there are 4 tests

[sauravhiremath]

Jest has now included

• incremental progress feature in its 26.2.0 release 🎉 (change testRunner config to jest-circus/runner)
  Ref: feat: report Individual Test Cases jestjs/jest#10227
  https://github.com/facebook/jest/blob/master/packages/jest-circus/README.md#installation

• Configurable thresholds by specifying them in projectConfig 🎉
  Ref: feat: add long test time threshold option jestjs/jest#9366

[aslushnikov]

This is no longer applicable since we switched off jest.