What's the difference between a testResultsProcessor and a reporter?

[SevenOutman]

What's different when I use jest-junit as a reporter v.s. a testResultsProcessor?

[palmerj3]

Very little. But the subtle difference is that a testResultsProcessor only receives details about test runs after all tests are finished.

Whereas a reporter has the ability to receive test results after individual tests and/or test suites are finished.

testResultsProcessor remains in jest because Facebook needs it internally (or so I've been told).

[SevenOutman]

So if I just want to generate a JUnit style report after all tests are finished (in my case for GitLab CI integration), it's merely no difference to use jest-junit as a testResultsProcessor or as a reporter. And when I need it to report dynamically after each test case (e.g. IDE integrations), I should only use it as a reporter. Am I getting it correct? At 2021-02-22 17:55:30, "Jason Palmer" <notifications@github.com> wrote: Very little. But the subtle difference is that a testResultsProcessor only receives details about test runs after all tests are finished. Whereas a reporter has the ability to receive test results after individual tests and/or test suites are finished. testResultsProcessor remains in jest because Facebook needs it internally (or so I've been told). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[palmerj3]

You should use it as a reporter. testResultsProcessor support is only there for legacy reasons but it could be removed in the future.

jest-junit only writes junit files at the end of a test run anyway.

[fatso83]

I think this could be better communicated in the docs, maybe even linking to this discussion 😄 I was wondering why the config only took effect when using it as a reporter, as opposed to configuring it as a testResultsProcessor.

[SimenB]

reporter is mentioned first, but I agree a sentence saying that using it as testResultsProcessor is discouraged is probably a good idea. PR? 😀

[palmerj3]

Using it as a reporter allows you a lot more flexibility in the future should you decide to use some of jest-junit's configuration options

[SevenOutman]

Thank you for the clear answers!

[zoltan-boros]

Back to the original question:

What's the difference between a testResultsProcessor and a reporter?

As per Jest API testResultsProcessor is string, whereas reporters is array. This implies that only one test result processor can be used at a time, whereas multiple reporters simultaneously. At least this is how I interpret the API.