Fix for #1573

[alfeg]

This PR closes #1573

Simple fix is suggested by @igvnv #1573 (comment)

This should cleanup console output during jest test run.

[Havunen]

Hmm, did you try this actually works? When inferno is bundled then those process env node env checks are replaced/removed

[alfeg]

Yeah my bad, Haven't checked actual output. Seems to be much more problematic. Sorry.

Those output messages are literally pollute tests output.

[igvnv]

I have prepared my PR for fix this issue and found his way:

// This message informs developers that they are using development mode (can happen
// in production because of bundling mistakes) and, therefore, Inferno is slower
// than in production mode. Skipping the notification for testing mode to keep testing
// console clear.
const testingEnv = process.env.JEST_WORKER_ID !== undefined;

if (process.env.NODE_ENV !== 'production' && !testingEnv) {

[Havunen]

Yeah @igvnv that could work, can you open PR for it please :)

[igvnv]

@Havunen to be honest, I little shy :) Is it OK to support Jest only? I am afraid that I have no time to test other popular testing libraries.

[Havunen]

Is it OK to support Jest only

Yeah I think this is jest only problem, because it bundles tests to multiple files and adds all dependencies to each file. Jasmine and mocha at least works without an issue