Improve reporter data for more powerful integrations

[mkcode]

Summary:

Richer reporters can improve feedback loop both by highlighting different things depending on what you’re working on (such as the current assertion being run, last assertion run), and by integrating better into existent tooling such as VS Code or WebStorm to get results directly in your editor. This project would explore in what ways Jest could emit useful data for reporters and integrations as well as implementing that.

Issue links:

• facebook/jest Expose more data in reporters for IDE integrations · Issue Expose more data in reporters for IDE integrations jestjs/jest#8840
• facebook/jest reading custom matcher result from custom reporter · Issue reading custom matcher result from custom reporter jestjs/jest#7594
• facebook/jest Use jest reporters to report more events · Issue Use jest reporters to report more events jestjs/jest#4471
• facebook/jest [RFC]: Rethinking reporters in Jest · Issue [RFC]: Rethinking reporters in Jest jestjs/jest#7900
• facebook/jest [RFC]: Rethinking reporters in Jest · Issue [RFC]: Rethinking reporters in Jest jestjs/jest#7900
• facebook/jest Work in progress PR: Add failureDetails property to circus test results · Issue Add failureDetails property to circus test results jestjs/jest#9496

Level of complexity: Medium

Experience wanted:

• JavaScript
• Jest testing framework

Deliverables:

• Determining what events would be useful - this should involve talking to maintainers of tooling such as VS Code and Webstorm
• Implement any new events or enrich the data of current events based on that research
• Rewriting Jest’s reporter API to be event based rather than making them implement an interface with anmed functions
  • Not strictly needed, but will make it easier to people to consume