Improve integ. with Jest in terms of logging

[d4vidi]

• This change has been discussed in issue Improve Jest's console output flow #1349 and the solution has been agreed upon with maintainers.

---

Description:

Fixes #1349.

[noomorph]

Sure, I'll review it tomorrow

[noomorph]

@d4vidi, I did a quick review of the PR.
There are a few points for the dialogue and a few assignments to me, as I was the one who messed with a couple of files.
But for the most part, that's it.

[noomorph]

Good morning, @d4vidi!

I've put some more thought into what is suggested by the PR, and actually, I'm coming to a conclusion that we might want to split this PR into two.

1. I absolutely approve the thing with Jest reporter (the one that flushes logs immediately), that is what I suggest to leave as a core of this pull request. I mentioned previously, that for the greater good we should consider suggesting that immediate flush configuration option to Jest project itself in the foreseeable future.
2. AFAIU, the Jasmine trace reporter is not tightly related to Detox. There a few projects on the Internet (namely, Github) that contribute their reporters to Jasmine:

• https://github.com/larrymyers/jasmine-reporters - see TerminalReporter. Has a few flaws though:
  • uses console.log instead of process.std*** (looks bad if you run inside Jest)
  • minor visual issues: mandatory "..." after test summary and no ability to flatten full name
• https://github.com/onury/jasmine-console-reporter - has other flaws:
  • too smart - it tampers with terminal output (deletes printed lines, etc). Might conflict with Jest.
  • while it has full test title flattening, it does not seem to work right.

So I conclude two thoughts out of this:

1. It's not that uncommon to create a separate jasmine reporter npm package. I think it's perfectly okay if we extract your trace reporter out of Detox project. In my opinion, maintaining it will be more flexible and fast and won't require releasing extra Detox versions. Detox Jest guide can encourage using it and we can add it to Jest example project.
2. As for where to extract it, I suggest wix-incubator at this stage. However, we might try luck with contributing PR to TerminalReporter (1) as all problems listed above can be solved by adding more configuration options, IMO. There is just a risk the repo is abandoned to some extent (the last commit was 8 months ago) or that accepting PR might take too long.

So your second PR (if we split #1351) might add an opinionated recommendation to try out the new trace reporter in some of the projects, as soon as the npm package with your jasmine trace reporter is ready.

[d4vidi]

@noomorph with my latest commit (399cb34) re adaptive specs-reporting, I'm done with this for now. Please review.

[noomorph]

I won't lie — to my taste, the current implementation still seems a bit rushed and not well polished.
However, in the light of the circumstances, since we want to roll it out sooner, and as long as it is technically working in a valid way, I have no strong objections to it, there's nothing blocking now, AFAIC.

So, consider it to be approved.