[Part 1] Individual Test Case Report - Support custom messages

[sauravhiremath]

Summary

PART 1 of 2

Aim: Support custom messages for jest worker
Fixes: #1
Ref: jestjs#9662

• The original PR by @rogeliog Add support for workers to send custom messages to parent in jest-worker jestjs/jest#9662 profoundly inspires the current PR.
• This sub-PR is an attempt to achieve Report progress of individual test cases jestjs/jest#6616
• As an independent PR, it allows custom messages to be sent to parent from the worker process using node event listeners

Note

It is an independent PR hence can be merged individually or can be stacked with other milestone PRs and merged together

Test plan

An extension from jestjs#9662

[sauravhiremath]

@jevakallio @kunal-kushwaha Could you try running yarn jest for this PR.

A single test case is always failing (in the CI build too). Any reasons why?

Test Result:

❯ yarn jest
yarn run v1.22.4
$ node ./packages/jest-cli/bin/jest.js
 FAIL  e2e/__tests__/customTestSequencers.test.ts (5.815 s)
  ● run prioritySequence first async

    expect(received).toBe(expected) // Object.is equality

    Expected: 0
    Received: 1

      48 |     {},
      49 |   );
    > 50 |   expect(result.exitCode).toBe(0);
         |                           ^
      51 |   const sequence = extractSummary(result.stderr)
      52 |     .rest.replace(/PASS /g, '')
      53 |     .split('\n');

      at Object.toBe (e2e/__tests__/customTestSequencers.test.ts:50:27)

 

[kunal-kushwaha]

@sauravhiremath: I'm also facing the same error 😕

[sauravhiremath]

Ahh @kunal-kushwaha no worries. I just resolved the issue, had to add async for running test sort. I didn't know test sequencer had an option to be run in async too. It's fixed now

Push coming in a bit :)

[sauravhiremath]

@jevakallio it works!! Could you have a look if any changes required?

[jevakallio]

@sauravhiremath nice! 🎉 I ran out of time today, will review this tomorrow morning!

[jevakallio]

@sauravhiremath I didn't review @rogeliog's commits because I have no context for them. I did review the cleanup commits you had made on top, and had some questions and notes on them.

Some comments I made were already changed in following commits you had made, so apologies if anything is redundant.

Overall, I'm seeing a lot of code style changes, but I don't understand why those changes were made? If they are to conform to Jest code standards or linter rules, that's good. But if not, the general advice I would have is not to change code for purely aesthetic reasons, unless there's a rationale for it.

[sauravhiremath]

@kunal-kushwaha , you can make this PR to facebook upstream if you want!

[kunal-kushwaha]

@sauravhiremath This looks great! Made one 🎉

[kunal-kushwaha]

Merged into master via upstream 🎉

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