[Bug]: Reporter.onTestCaseResult not called for test.todo in Jest 27

[segrey]

Version

27.4.5

Steps to reproduce

Reporter.onTestCaseResult doesn't get called on test.todo.

// my.test.js
test.todo('my todo');
test('my test', () => {});

// my-reporter.js
class MyReporter {
    onTestCaseResult(test, testCaseResult) {
        console.log('onTestCaseResult: ' + testCaseResult.title);
    }
}

module.exports = MyReporter;

Expected behavior

jest --reporters ./my-reporter.js should print:

Determining test suites to run...onTestCaseResult: my test
onTestCaseResult: my todo

Actual behavior

Actually, jest --reporters ./my-reporter.js prints:

Determining test suites to run...onTestCaseResult: my test

Additional context

No response

Environment

System:
    OS: Linux 5.4 Linux Mint 20.2 (Uma)
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
    Yarn: 1.22.17 - /usr/bin/yarn
    npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
  npmPackages:
    jest: ^27.4.5 => 27.4.5

[segrey]

This caused https://youtrack.jetbrains.com/issue/WEB-51467. A workaround will be added in WebStorm 2021.3.2: test.todo will be fetched from onTestFileResult events, but it happens too late, when the whole test file is done. Would be great to fix this issue, i.e. fire onTestCaseResult events for test.todo.

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

[SimenB]

This seems reasonable to fix.