[Part 2] Individual Test Case Report - Report progress of individual test cases

[kunal-kushwaha]

Summary

Part 2 of 2

Aim: Report progress of individual test cases (this is the final milestone PR)
Reference: jestjs#9001
Fixes: jestjs#6616 #1

Breakdowns:

• [Part 1] Individual Test Case Report - Support custom messages #5 --> Add support for workers to send custom messages to parent in jest-worker

Test plan

• Add custom message support in jest-worker
• Using event handler for parallel workers
• Update onCustomMessage functions to pass tests (caused by updating its Type)
• Get on Fixes recommended
• Add Tests
• Update documentation

Update so far:

Running JEST_CIRCUS=1 yarn jest should increment atomic tests and not batch update them as it did before.

TODO

• Write more e2e tests
• Update Documentation
• Figure out why this test is failing:
  To Reproduce: $ JEST_CIRCUS=1 yarn test-leak

    Test suite failed to run

    EXPERIMENTAL FEATURE!
    Your test suite is leaking memory. Please ensure all references are cleaned.

    There is a number of things that can leak memory:
      - Async operations that have not finished (e.g. fs.readFile).
      - Timers not properly mocked (e.g. setInterval, setTimeout).
      - Keeping references to the global scope.

      at onResult (packages/jest-core/build/TestScheduler.js:190:18)
          at Array.map (<anonymous>)

[kunal-kushwaha]

@SimenB, @jevakallio: Review is requested and suggestions on changes to be made if any. There's just 1 e2e test failing but rest of the things are working as expected.

Running JEST_CIRCUS=1 yarn jest should increment atomic tests and not batch update them like it did before.

[SimenB]

This is really shaping up, great work!

[kunal-kushwaha]

Reference: jestjs#10227

[kunal-kushwaha]

Merged into master and rebased the fork 🎉

[github-actions]

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.